Investigate using shadow DOM to hide Remote L10n translations for from local translations
Categories
(Firefox :: Messaging System, defect, P2)
Tracking
()
People
(Reporter: andreio, Assigned: andreio)
References
Details
Attachments
(1 file)
Why: we would be able to use HTML markup in our remote translations. For context any messaging surface that uses Remote L10n now cannot support HTML markup.
The global Localization instance does not expect another one (like the Remote L10n one) to exist and will overwrite our translations. We can hide content from it by using custom elements and then connecting the root to the Remote L10n localization. By default the mutation observer does not check the shadow DOM.
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
Comment 3•5 years ago
|
||
Backed out changeset 7afc6bac547c (bug 1616280) for browser-chrome failures at dom/l10n/DOMLocalization.cpp
Backout: https://hg.mozilla.org/integration/autoland/rev/6aa0ab986adc18ef357b57d48913531a9e874577
Failure push: https://treeherder.mozilla.org/#/jobs?repo=autoland&revision=7afc6bac547c9a5135c40c07cb05de6905caf034
Failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=298119543&repo=autoland&lineNumber=3873
Comment 5•5 years ago
|
||
bugherder |
Updated•5 years ago
|
Comment 6•5 years ago
|
||
Since the status are different for nightly and release, what's the status for beta?
For more information, please visit auto_nag documentation.
Assignee | ||
Updated•5 years ago
|
Updated•5 years ago
|
Description
•