-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improvements to the editor with multiple roots example and guide #1599
Comments
It is fine for me to focus one element. But to clarify what I meant:
I believe that there was a reason why it was created as a single multi-root editor, not by multiple separated editor. And I believe that the reason was to provide the single-editor experience. This is why I suggest that the editor should act like this - like a single editor.
That's a good point, in fact. |
Anyway, check out screencasts in #1600 (comment). |
Isn't this ticket a DUP of #1596 (or vice versa)? |
This one is a DUP but since there's a lot going on here already, I marked the other one as DUP. |
Feature: Made `FocusTracker#focusedElement` observable to bring support for multi-root editors (see ckeditor/ckeditor5#1599).
Docs: Improvements to the editor with multiple roots example and guide. Closes #1599.
A follow–up of
cc @pjasiun @f1ames
As for #1586 (comment)
The user does not care what's underneath. They navigate and fill the text in a form and the expect things to behave like a form. They focus one field at a time and they expect just a single field to be visually focused.
Besides, this way it's very hard to tell which editable (form field) is focused (Where's my caret? Am I typing the email address or the message yet?).
The text was updated successfully, but these errors were encountered: