Closed Bug 1481882 Opened 6 years ago Closed 6 years ago

Load customElements.js in chrome HTML documents (remove XUL contentType restriction)

Categories

(Firefox :: General, task, P3)

task

Tracking

()

RESOLVED FIXED
Firefox 63
Tracking Status
firefox63 --- fixed

People

(Reporter: bgrins, Assigned: bgrins)

References

Details

Attachments

(1 file)

Right now we only load the chrome Custom Elements in XUL documents (https://searchfox.org/mozilla-central/rev/f0c15db995198a1013e1c5f5b5bea54ef83f1049/toolkit/components/processsingleton/MainProcessSingleton.js#82). This was done because we get errors when attempting to register them in HTML documents. Those errors will be fixed by Bug 1480465. We should be careful to not load it in about:blank windows, or at least those loaded during early startup as per https://bugzilla.mozilla.org/show_bug.cgi?id=1442006#c12 and https://bugzilla.mozilla.org/show_bug.cgi?id=1411707#c45.
Priority: -- → P3
Assignee: nobody → bgrinstead
Status: NEW → ASSIGNED
This provides support for using XUL elements in chrome XHTML documents, including the experimental xhtml browser window (browser.xhtml).
Comment on attachment 9001367 [details] Bug 1481882 - Load customElements.js in chrome XHTML documents;r=mossop Dave Townsend [:mossop] has approved the revision.
Attachment #9001367 - Flags: review+
Pushed by bgrinstead@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/5a85654da581 Load customElements.js in chrome XHTML documents;r=mossop
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 63
Type: enhancement → task
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: