Up/down keyboard navigation jumps horizontally

[mcsf]

See also: #53416 #44055

Description

Step-by-step reproduction instructions

The horizontal caret position is not properly preserved across paragraph jumps. All three browsers behave differently. See the attached videos, in which I place the caret at the end of the last paragraph and then just press Up repeatedly.

Chrome seems to be the best-behaved browser so far:

caret-chrome.mov

Firefox gets it almost right, but then note the jump to "placeat" and then to "maxime":

caret-firefox.mov

Safari is all over the place, seemingly always setting the caret's horizontal component to match the end of the curernt paragraph:

caret-safari.mov

Screenshots, screen recording, code snippet

No response

Environment info

Gutenberg trunk, etc.

Please confirm that you have searched existing issues in the repo.

Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

Yes

[ellatrix]

@mcsf Could you create separate issues for these? :)

[ellatrix]

I don't think there's anything we can do here, except for using the wrapper contenteditable trick. Safari gives us a wrong range for document.caretRangeFromPoint( x, y ), so 🤷‍♀️

[mcsf]

@mcsf Could you create separate issues for these? :)

Done: I extracted the second issue Into #53416 and kept the first one here.

[bph]

@mcsf I am getting confused. Could you please verify if this issue was solved with?

• Writing flow: fix vertical arrow keys not moving #53454

If not, what's the likelihood this issue is tackled for the upcoming 6.4 release?

[mcsf]

Could you please verify if this issue was solved with?

No, the issue is still present. #53454 wasn't really concerned with it.

If not, what's the likelihood this issue is tackled for the upcoming 6.4 release?

As Ella says, fixing this requires reimplementing caret movement with the contentEditable trick. Considering all the little things we'd like to get in 6.4, I would say it's more likely that this issue will not be fixed by then.

[bph]

Thank you so much @mcsf - I moved this issue to the Punt to 6.5 column on the WordPress 6.4 board.

[annezazu]

After a review by core editor triage leads and core editor tech leads, this has been removed from the board for 6.5 consideration.