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

RESOLVED FIXED in Firefox 63

Status

()

task
P3
normal
RESOLVED FIXED
10 months ago
12 days ago

People

(Reporter: bgrins, Assigned: bgrins)

Tracking

(Blocks 1 bug)

unspecified
Firefox 63
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox63 fixed)

Details

Attachments

(1 attachment)

Assignee

Description

10 months ago
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

Updated

10 months ago
Assignee: nobody → bgrinstead
Status: NEW → ASSIGNED
Assignee

Comment 1

10 months ago
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+

Comment 3

10 months ago
Pushed by bgrinstead@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/5a85654da581
Load customElements.js in chrome XHTML documents;r=mossop

Comment 4

10 months ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/5a85654da581
Status: ASSIGNED → RESOLVED
Closed: 10 months ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 63

Updated

12 days ago
Type: enhancement → task
You need to log in before you can comment on or make changes to this bug.