Select Language combobox is autofocused on about:translations page load
Categories
(Firefox :: Translations, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox150 | --- | fixed |
People
(Reporter: ayeddi, Assigned: nordzilla)
References
(Blocks 1 open bug,
URL
)
Details
(Keywords: access)
Attachments
(2 files, 2 obsolete files)
STR:
- open Firefox Nightly 150
- type in "about:translations" in the URL bar
- press
Enterand observe the behavior of keyboard focus - repeat steps 2-3 with a screen reader running (i.e. NVDA on WinOS) and observe the screen reader's announcement
Expected:
- focus should be placed, by default, to the web content (web page's container, as it is done for the
about:profilespage, for instance). Autofocus is, generally, not expected.
Actual:
Select languagecombobox is autofocused - it forces users to missLearn morelink andDetect languagecombobox that are placed in the focus order before the autofocused control
| Assignee | ||
Updated•3 months ago
|
| Assignee | ||
Comment 1•3 months ago
|
||
This commit removes the custom initial-focus logic from the about:translations
page, letting the page set its own default focus, starting from the top.
This is much better for assistive technology, since it ensures that screen
readers will pick up the crucial context at the top of the page, including
the top-level learn-more link.
Updated•3 months ago
|
| Assignee | ||
Comment 2•3 months ago
|
||
This commit removes the custom initial-focus logic from the about:translations
page, letting the page set its own default focus, starting from the top.
This is much better for assistive technology, since it ensures that screen
readers will pick up the crucial context at the top of the page, including
the top-level learn-more link.
Updated•3 months ago
|
| Assignee | ||
Comment 3•3 months ago
|
||
This commit removes the custom initial-focus logic from the about:translations
page, letting the page set its own default focus, starting from the top.
This is much better for assistive technology, since it ensures that screen
readers will pick up the crucial context at the top of the page, including
the top-level learn-more link.
Updated•3 months ago
|
Comment 6•3 months ago
|
||
Backed out for causing bc failures @ browser_MLSuggest_integration.js
Backout link: https://hg.mozilla.org/integration/autoland/rev/718045fa26c6d81479609edd23eb98c790b4f95e
Failure log -> browser/components/urlbar/tests/browser/browser_MLSuggest_integration.js
| Assignee | ||
Comment 7•3 months ago
|
||
This is part of a single backout that spanned multiple bugs.
In the patch stack, I increased the timeout when waiting for a mocked RemoteSettings model to download within our Translations tests, hoping that it might also help to reduce intermittent Translations test failures.
There are a few ml related tests that share our Remote Settings mocks. This test case happens to wait for the full duration of the timeout as part of the success path of the test case.
I've reverted the timeout change, and everything should hopefully be fine now.
I would one day like to either fully separate this code, or unify it in a way that ml doesn't rely on Translations under the hood, so that its more clear where the downstream consumers are.
| Assignee | ||
Comment 8•3 months ago
|
||
Restoring the original timeout seems to have fixed the issue:
- https://hg.mozilla.org/try/rev/f90e8c8356a1b6f859b28cf430158700cbf43901
- https://treeherder.mozilla.org/jobs?repo=try&revision=c4b57d3456613bf4d05a01e04ce95a3679a2c8db
Attempting re-landing.
Comment 10•3 months ago
|
||
| bugherder | ||
Updated•2 months ago
|
Description
•