Closed Bug 1616280 Opened 5 years ago Closed 5 years ago

Investigate using shadow DOM to hide Remote L10n translations for from local translations

Categories

(Firefox :: Messaging System, defect, P2)

defect

Tracking

()

RESOLVED FIXED
Firefox 77
Tracking Status
firefox74 --- wontfix
firefox75 --- wontfix
firefox76 --- wontfix
firefox77 --- fixed

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.

Priority: -- → P2
Target Milestone: --- → Firefox 75
Assignee: nobody → andrei.br92
See Also: → 1617669
Blocks: 1630907
Pushed by aoprea@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/7afc6bac547c Use shadow DOM to hide Remote L10n translations for from local translations r=k88hudson
Pushed by aoprea@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/9e7bb5bc539b Use shadow DOM to hide Remote L10n translations for from local translations r=k88hudson
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: Firefox 75 → Firefox 77

Since the status are different for nightly and release, what's the status for beta?
For more information, please visit auto_nag documentation.

Flags: needinfo?(andrei.br92)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: