![]() ![]() As we were fixing those issues, making the keyboard navigation better, it struck us that it was unnecessary hard to exit “edit” mode with the keyboard only the only way to do this was with the Esc key, but that also reverts any changes that was made in the text input! What I ended up doing most of the time is do validate with Enter, which moves the focus to the next input, then hit Esc to opt-out of the edit mode. One of the area we focused on was the Inspector, and especially keyboard navigation in the Rules view. In 2023 the Accessibility team at Mozilla ran an audit on DevTools and created a list of issues that needed to be fixed. ![]() This behavior seems to exist since the Firebug days and every browsers Developers Tools implemented it, as it allowed to quickly edit multiple properties in a rule without leaving the keyboard. Previously, when the user hit Enter, we advanced the editor to the next editable property, which is also directly turned into a text input. When you click on a selector, a property name or a property value, a text input appears to modify the underlying value. Previously, this will have enabled the edit mode on the color property. The value element is now focused (hence the focus indicator). The Rules view after the background-color value was modified and validated with the Enter key. You can still use Ctrl + Enter ( Cmd + Enter on macOS) or Tab to validate and move the focus to the next input. ![]() ![]() Starting Firefox 122, when editing a selector, a property name or a property value in the Inspector, the Enter key will no longer move the focus to the next input, but will validate what was entered and focus the matching element ( #1861674). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |