Display Unsupported Detected Language Info Message in about:translations
Categories
(Firefox :: Translations, enhancement, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox150 | --- | fixed |
People
(Reporter: nordzilla, Assigned: nordzilla)
References
(Blocks 1 open bug)
Details
Attachments
(5 files)
Description
The about:translations design (internal only) has never displayed a proper info message if the detected language is not yet supported for translation.
Now that we are redesigning the UI, we should ensure that it has a proper UI info message if the detected language is not supported.
| Assignee | ||
Updated•10 months ago
|
| Assignee | ||
Comment 1•7 months ago
|
||
This commit removes the catch-all AnyEventDetail option from
existing about:translations tests. We can, and should, be fully
deterministic and specific about any event details that we assert.
| Assignee | ||
Comment 2•7 months ago
|
||
about:translations has requirements that the focus outline should be
around the entire section, which may contain a textarea and a copy
button, for example. This commit attempts to move more of that handling
into the CSS, rather than the JavaScript code.
| Assignee | ||
Comment 3•7 months ago
|
||
This commit makes our section-height assertions more rigorous,
rather than only asserting that the heights increased or decreased,
we now make assertions against the actual pixels.
| Assignee | ||
Comment 4•7 months ago
|
||
This commit adds a new error message that shows within the
target section if a translation request fails.
Updated•7 months ago
|
Updated•7 months ago
|
Updated•7 months ago
|
Updated•7 months ago
|
| Assignee | ||
Comment 5•7 months ago
|
||
This commit contains various miscellaneous fixes within
the Translations tests that should hopefully improve
intermittent test failures and better guard against
race conditions within the test code.
Updated•7 months ago
|
Updated•7 months ago
|
Updated•7 months ago
|
Updated•7 months ago
|
Updated•7 months ago
|
Comment 8•7 months ago
|
||
Backed out for causing bc failures @ browser_MLSuggest_integration.js
Backout link: https://hg.mozilla.org/integration/autoland/rev/2d97cc387177f9e37822209df483fce769193384
Failure log -> browser/components/urlbar/tests/browser/browser_MLSuggest_integration.js
| Assignee | ||
Comment 9•7 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 10•7 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 11•7 months ago
|
||
Comment 12•7 months ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/5afc0a529e6f
https://hg.mozilla.org/mozilla-central/rev/02615c33a5e5
https://hg.mozilla.org/mozilla-central/rev/403ec39812da
https://hg.mozilla.org/mozilla-central/rev/1a781f928214
https://hg.mozilla.org/mozilla-central/rev/53b09c82a87c
Updated•6 months ago
|
Description
•