Skip to content

Accessibility: Avoid Keyboard trap on the editor content#1359

Merged
youknowriad merged 1 commit intomasterfrom
fix/tab-placeholder-trap
Jun 22, 2017
Merged

Accessibility: Avoid Keyboard trap on the editor content#1359
youknowriad merged 1 commit intomasterfrom
fix/tab-placeholder-trap

Conversation

@youknowriad
Copy link
Copy Markdown
Contributor

closes #1357

When the placeholder receives the focus, it is transformed into a text block and creating a new placeholder right after creating a tab trap.

The fix here keeps the behaviour of transforming to text block on focus only if the post content is empty. If the post content is not empty, you'll need to click "Enter" or mouse click to trigger the transformation.

@youknowriad youknowriad added [Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). [Type] Bug An existing feature does not function as intended labels Jun 22, 2017
@youknowriad youknowriad self-assigned this Jun 22, 2017
@youknowriad youknowriad requested review from afercia and jasmussen June 22, 2017 11:09
@afercia
Copy link
Copy Markdown
Contributor

afercia commented Jun 22, 2017

Quickly tested on Mac Chrome, Firefox, Safari: the keyboard trap is fixed, testing in the new, empty, post seems I end up with two empty blocks, is this expected?

screen shot 2017-06-22 at 15 18 48

Copy link
Copy Markdown
Contributor

@afercia afercia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The keyboard trap is fixed, one question: see comment

@youknowriad
Copy link
Copy Markdown
Contributor Author

@afercia This is not two empty blocks. This is an empty block and a placeholder that eventually will be transformed into a block if we hit enter or click. This is expected.

@youknowriad youknowriad merged commit 401e683 into master Jun 22, 2017
@youknowriad youknowriad deleted the fix/tab-placeholder-trap branch June 22, 2017 13:50
youknowriad pushed a commit that referenced this pull request Jan 17, 2020
Merge master (v1.12.0) back to develop
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). [Type] Bug An existing feature does not function as intended

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Keyboard trap on the editor content

2 participants