Handle about:translations select keyboard navigation
Categories
(Firefox :: Translations, task, P2)
Tracking
()
People
(Reporter: nordzilla, Assigned: nordzilla)
References
(Blocks 1 open bug)
Details
Description
There is no "translate" button on the about:translations page to trigger a translate action. In many cases, the translation begins automatically when a valid language pair is selected.
When using the mouse, this doesn't present an issue, because the dropdown menu opens up, and you select exactly the language that you want. Keyboard navigation is a different story. Some operating systems, such as Linux, allow you to use Alt + Arrow to open the dropdown and select a language, but the default behavior is to directly switch the selected value to the next language.
We need to prevent the default behavior in this case, and wait until the user tabs to focus the source text area, before triggering the translation.
This is very similar to how the SelectTranslationsPanel works.
|
Assignee | |
Updated•3 months ago
|
|
|
Assignee | |
Updated•3 months ago
|
|
|
Assignee | |
Comment 1•1 month ago
|
||
Since we've decided to use moz-select for this project, we can't do the exact same kind of custom logic that the SelectTranslationsPanel currently does with the XUL menulist.
The current, default moz-select keyboard navigation is fine for the initial release.
For macOS there is no issue, since you can only open the dropdown with the keyboard.
For Windows and Linux, keyboard users can use Alt + Arrow to open the dropdown.
Everything is still functional without using Alt + Arrow, but it may end up loading more models than intended as the page logic cycles through the languages.
Description
•