Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Core Committers: Use this line as a base for the props when committing in SVN: To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Test using WordPress PlaygroundThe changes in this pull request can previewed and tested using a WordPress Playground instance. WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser. Some things to be aware of
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation. |
fcbdba9 to
030e8ba
Compare
030e8ba to
047430f
Compare
|
Video recording to illustrate the behavior with mouse and keyboard. Tested on Safari. Observe any previous selection and caret position is preserved. I uset a custom focus style for the Screen.Recording.2026-09-18.at.12.04.40.mov |
…d to switch editor mode. Pointing device (mouse, touch, etc.) users benefit from focus being moved to the editor when switching it from Visual to Code mode and vice-versa, as they can just keep typing without loosing the previous caret position or selection. However, moving focus is confusing and distracting to keyboard and screen reader users as they loose their place. In this case, focus should stay on the switch buttons. Previous caret position or selection is preserved in both cases. Developed in #13560 Props shreya0shrivastava, dannerjamanca, arkaprabhachowdhury, afercia. Fixes #42540. git-svn-id: https://develop.svn.wordpress.org/trunk@63759 602fd350-edb4-49c9-b593-d223f7449a82
…d to switch editor mode. Pointing device (mouse, touch, etc.) users benefit from focus being moved to the editor when switching it from Visual to Code mode and vice-versa, as they can just keep typing without loosing the previous caret position or selection. However, moving focus is confusing and distracting to keyboard and screen reader users as they loose their place. In this case, focus should stay on the switch buttons. Previous caret position or selection is preserved in both cases. Developed in WordPress/wordpress-develop#13560 Props shreya0shrivastava, dannerjamanca, arkaprabhachowdhury, afercia. Fixes #42540. Built from https://develop.svn.wordpress.org/trunk@63759 git-svn-id: http://core.svn.wordpress.org/trunk@62931 1a063a9b-81f0-0310-95a4-ce76da25c4cd
Trac ticket: https://core.trac.wordpress.org/ticket/42540
Prevents setting focus to the Classic editor when switching 'Visual' and 'Code' mode by using a keyboard (actually a non-pointing device).
Use of AI Tools
None
This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.