Open Bug 1280672 Opened 9 years ago Updated 9 years ago

Add content-privileged HTML support

Categories

(L20n :: JS Library, defect)

Product:
L20n
Component:
JS Library
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
ASSIGNED

People

(Reporter: stas, Assigned: stas)

References

(Depends on 1 open bug)

Details

(Whiteboard: [gecko-l20n])

User Story

L20n in Gecko should support content-privileged HTML documents.
L20n in Gecko should support content-privileged HTML documents.
Depends on: 1280687
Content-privileged l20n.js needs to somehow talk to the L10nRegistry to make IO calls. Contrary to l20n-chrome-html (bug 1280670), it cannot Cu.import the Registry and talk to it directly. The solution is to use events which communicate with the registry via a content script injected into the browser frame. This is similar to how the UITour works, or to the PoC implemented on the gecko-dev/l20n branch for demoing live updates and the interactive localization during MozLondon. An experimental version of this approach landed on the branch in: https://github.com/mozilla/gecko-dev/commit/353b3567243016f834a8f519ecb7b94c9d06dd27 It still uses the L20nDemo component. I'll switch it to the L10n Message Relay from bug 1280687 soon.
Assignee: nobody → stas
Status: NEW → ASSIGNED
Mass change dependency tree for bug 1279002 into a whiteboard keyword.
No longer blocks: gecko-l20n
Whiteboard: [gecko-l20n]
You need to log in before you can comment on or make changes to this bug.