Enter no longer creates sibling toggles when parent is expanded
Description:
I've noticed a regression in the keyboard behaviour of toggle blocks that previously worked correctly approximately five major updates ago.
Steps to reproduce:
Create a parent toggle using >f.
Press Ctrl + Enter to create a nested toggle beneath it.
Return to the parent toggle while keeping it expanded.
Press Enter.
Current behaviour:
Enter creates a new nested toggle beneath the parent rather than a sibling toggle at the same indentation level.
Previous / Expected behaviour:
Previously, pressing Enter while editing the parent toggle created a new sibling toggle at the parent's indentation level, even when the parent was expanded.
Ctrl + Enter was used to deliberately create nested content.
Video Evidence:
I've attached a screen recording demonstrating the issue.
The recording shows how pressing Enter while editing an expanded parent toggle incorrectly creates a nested toggle instead of a sibling toggle.
This behaviour previously worked as expected approximately five major updates ago, so I believe this is a regression rather than an intentional design choice.
Recording 2026-10-26 192444.mp4
Capacities v1.72.4; none none; Windows v10; Chrome v148.0.7778.280 (WebKit v537.36); Desktop (Electron); 26/10/2026, 19:26:42
1 Comment
Sign in to comment

Hi, thanks for the feedback. I checked with the team and this is expected behaviour following some editor changes that were made in a previous release. I will close this ticket as a result.