Skip to content
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

Deep dive for focus tracking #6087

Closed
Reinmar opened this issue Jan 20, 2020 · 0 comments · Fixed by ckeditor/ckeditor5-ui#552
Closed

Deep dive for focus tracking #6087

Reinmar opened this issue Jan 20, 2020 · 0 comments · Fixed by ckeditor/ckeditor5-ui#552
Assignees
Labels
domain:accessibility This issue reports an accessibility problem. type:docs This issue reports a task related to documentation (e.g. an idea for a guide).

Comments

@Reinmar
Copy link
Member

Reinmar commented Jan 20, 2020

📝 Provide a description of requested docs changes

Some goals:

  • Introducing what focus is and how important it is for an editor and UI/UX/a11y. Differentiating focus and selection.
  • Introducing focus tracking in the engine:
    • Focus observer (mention what it is but also that it uses capturing and listens on the editable)
    • focus/blur events
    • various isFocused properties
  • Introducing focus tracking in the UI:
    • Focus tracker
    • Focus cycler
  • Introducing editor's focus tracker:
    • editor.ui.focusTracker
    • Why do we need it?
    • How do plugins use it (register there, listen there)?
  • A real-life example of all that in practice. For instance, what happens step by step when you click in the editor, press Cmd+L, type the URL and submit it. Where is the focus at each step, what's fired and what's the state of most important properties.
  • PS. I feel that we should also provide here an answer for "how to focus the editor" as this guide may end up high in SERP for focus oriented queries. Potentially, this question can be answered at the very beginning of this guide or very end.
@Reinmar Reinmar added type:docs This issue reports a task related to documentation (e.g. an idea for a guide). status:confirmed labels Jan 20, 2020
@Reinmar Reinmar added this to the iteration 29 milestone Jan 20, 2020
@Reinmar Reinmar modified the milestones: iteration 29, iteration 30 Feb 24, 2020
@Reinmar Reinmar modified the milestones: iteration 30, iteration 31 Mar 10, 2020
Reinmar added a commit to ckeditor/ckeditor5-ui that referenced this issue Apr 7, 2020
Docs: Created the "Deep dive into focus tracking" guide. Closes ckeditor/ckeditor5#6087.
Reinmar added a commit that referenced this issue Apr 7, 2020
Docs: Mentioned the "Deep dive into focus tracking" guide in the "UI library" guide (see #6087).
Reinmar added a commit to ckeditor/ckeditor5-utils that referenced this issue Apr 7, 2020
Docs: Linked to the "Deep dive into focus tracking" from the FocusTracker class docs (see ckeditor/ckeditor5#6087).
mlewand pushed a commit that referenced this issue May 1, 2020
Docs: Created the "Deep dive into focus tracking" guide. Closes #6087.
mlewand pushed a commit that referenced this issue May 1, 2020
Docs: Linked to the "Deep dive into focus tracking" from the FocusTracker class docs (see #6087).
@Reinmar Reinmar added the domain:accessibility This issue reports an accessibility problem. label Oct 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
domain:accessibility This issue reports an accessibility problem. type:docs This issue reports a task related to documentation (e.g. an idea for a guide).
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants