coolest boy! happy birthday to mini scoresby!!

idk they taught me that I could move my shoulders and arms a bit to correct my posture

i might crack a bone so i don’t think so

I wish, at some random point during the video it requires a click, on a moving button, to confirm the presence.

Worst of it all, I can’t use the JS console because it’s basically some sort of VNC connection to protect from skips.

Almost did all of the 8 hours of the safety at work course, after procrastinating its start for almost 3 months.

that's a nice enhancement

k00b couldn’t merge my fix because I didn’t finish testing it yesterday, I suppose it’ll be deployed today!

Sorry for the inconvenience, I just wanted to make sure everything was fine before breaking it … again

a LIT saturday

I think it makes sense for the editor to be cut at the bottom, but not at the top lol.

The problem was that some browsers scroll to the caret not the element. I address this in this PR

yesterday I finally succeeded in reproducing it on Brave (osx)

1. go here
2. focus the first editor
3. scroll down
4. write something
5. editor is shadowed by the topbar.

the fix is all about telling the browser that we need from 60px (topbar + padding) to 90px (topbar + padding + editor toolbar) of space at the top when scrolling.

PR #2815

Hey if autoscroll is working for everything but not for our editor, then the problem is our editor, not the autoscroll!

Will get back to you once I got a fix ^^

😭

Autoscroll on text boxes is a browser native feature, as such we’re not controlling any of it.

This does not happen on the browsers I’m using (Safari, Brave), at least to the extent of my testing capabilities (lol). Anyhow this might happen, we’ll want to make sure the editor never gets shadowed by the sticky bar so let’s see if your suggestion can be applied ^^

What is your browser?

Got it! On it.

👀👀👀 I’m going to be honest, I’m failing in imagining a scenario in which the top bar gets stuck there or you can’t just scroll.

I’ll get back to my trench in a bit, and I’ll try to find a solution. In the meantime can you give me more details on what’s going on?

They don’t say it anywhere but I suppose they’re turning each HTML node into a universal tree and then convert that tree into Markdown (HAST -> MDAST)^[1].

That’s what we’ve been doing!
Instead of HTML nodes we’re mapping Lexical rich text nodes into Markdown (and viceversa).

edit: but there are many other methods to achieve this conversion, so I don’t know!

1. ASTs: Abstract Syntax Tree; H for HTML and MD for Markdown ↩

good luck!

cool AF -♾️

Stage 3 of the new editor, preview is changing its personality

See? You get me lol

My metaphor might be dramatic but I also think that we're not removing anything that wasn't there before.