You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Place the cursor after a newly created nested entry
#637
We have a client using nested entries to build long, complex reports. Our internal QA just flagged that when a new nested entry is created from “Add nested content,” the cursor returns to the spot before the new card, so the next block or paragraph lands above it. That’s consistent with leaving the cursor where it was, but it differs from editing a card (the cursor moves after it) and from CKEditor’s own widgets like images and tables. In long-form fields it means authors adding several blocks in a row get them in reverse order unless they click below each card first. Would you consider moving the cursor after the new card, or making it configurable?
For reference, the edit flow uses writer.createPositionAfter(modelElement) when its slideout closes, while the create flow sets the selection at the new card’s own index (“set position on before the card we just created” in entriesui.js, around line 413 in 5.9.0).
Steps to reproduce:
In a CKEditor field with nested entry types, place the cursor at the end of a paragraph.
Click “Add nested content”, pick an entry type, fill it in, and save the slideout.
Without clicking anywhere, add another nested entry the same way.
The second card is inserted above the first. Typing after step 2, instead of adding a second card, also lands above the new card.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
We have a client using nested entries to build long, complex reports. Our internal QA just flagged that when a new nested entry is created from “Add nested content,” the cursor returns to the spot before the new card, so the next block or paragraph lands above it. That’s consistent with leaving the cursor where it was, but it differs from editing a card (the cursor moves after it) and from CKEditor’s own widgets like images and tables. In long-form fields it means authors adding several blocks in a row get them in reverse order unless they click below each card first. Would you consider moving the cursor after the new card, or making it configurable?
For reference, the edit flow uses
writer.createPositionAfter(modelElement)when itsslideoutcloses, while the create flow sets the selection at the new card’s own index (“set position on before the card we just created” inentriesui.js, around line 413 in 5.9.0).Steps to reproduce:
All reactions