Display Unsupported 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
(3 files)
Description
The new about:translations design (internal only) includes an error message with a learn-more button when the device does not support Translations.
| Assignee | ||
Updated•10 months ago
|
| Assignee | ||
Updated•7 months ago
|
| Assignee | ||
Comment 1•7 months ago
|
||
This commit makes improvements to the scheduling algorithm
around reacting to user input in the source text area.
There are now 3 priorities of actions that occur.
- Actions that happen every time an input occurs.
- Actions that are throttled while input continually occurs.
- Actions that are debounced and take place after input stops.
| Assignee | ||
Comment 2•7 months ago
|
||
This commit adds a new info message to the source section if the
detected language of the source text is not a language that we
support for translation.
It also removes the condition on the confidence of the detection,
allowing for more continuous feedback to the user as they're typing
now that we have a UI-facing message about language support.
Updated•7 months ago
|
| Assignee | ||
Comment 3•7 months ago
|
||
This commit removes an unused learn-more button from the message bar
that displays when the device hardware is unsupported. The page that
we would go to is the same page as the primary learn-more link above.
Updated•7 months ago
|
Updated•7 months ago
|
Updated•7 months ago
|
Updated•7 months ago
|
Updated•7 months ago
|
Updated•7 months ago
|
Comment 6•7 months ago
|
||
Backed out for causing bc failures @ browser_MLSuggest_integration.js
Backout link: https://hg.mozilla.org/integration/autoland/rev/97cc667f93e96ab7a3f24820356357de6c0ebf6f
Failure log -> browser/components/urlbar/tests/browser/browser_MLSuggest_integration.js
| Assignee | ||
Comment 7•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 8•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 10•7 months ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/3e36743e6c56
https://hg.mozilla.org/mozilla-central/rev/7828930caa5e
https://hg.mozilla.org/mozilla-central/rev/dded11dd36ac
Updated•6 months ago
|
Description
•