Zoom Out Mode Prevents Navigation to Next Paragraph

[pitamdey]

Description

In Zoom Out mode, when a user clicks to enter a new paragraph, they are unable to navigate to the next paragraph but at the side bar i can see new paragraph is added. This issue disrupts the usual flow of content editing and may hinder the user experience.

Step-by-step reproduction instructions

1. Open Editor
2. Click on Zoom Out Mode
3. Click Enter on the paragraph
   ( Now you can see you will not move to next paragraph but in Document Overview I can see paragraph block is added )

Screenshots, screen recording, code snippet

https://www.loom.com/share/bcb95b970e194b24946dc7767fa9e2b7?sid=f9d06ce0-5301-429c-8331-a1a1eb8f1831

Environment info

No response

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

Please confirm which theme type you used for testing.

• Block
• Classic
• Hybrid (e.g. classic with theme.json)
• Not sure

[Mayank-Tripathi32]

Hey, I successfully replicated the bug and encountered a similar issue when deleting a paragraph tag, where the editor kept losing focus after each deletion.

I believe this happens because the focus isn't being set correctly due to viewport changes. I’ve identified a solution and will be opening a PR shortly.

[mikachan]

I think this has been fixed by #68106, as I can't seem to replicate this issue anymore on trunk. Do you see the same, or can you still replicate this?

[Mayank-Tripathi32]

@mikachan I am able to still replicate the issue on latest trunck branch

Screen.Recording.2024-12-20.at.10.22.23.PM.mov

[mikachan]

Ah yes I see the same now on trunk, I think I must've still had the changes from your PR applied 😅

[Mayank-Tripathi32]

How should we proceed with this? I believe the changes I made address the issue, but I’m unsure if this is the ideal behavior for the Zoom Out View. Would appreciate some feedback or suggestions to move forward or drop the PR.

[scruffian]

Trying a different fix here: #68245