Closed
Bug 1446557
Opened 8 years ago
Closed 7 years ago
Enable custom elements in trusted HTML documents by default
Categories
(Core :: DOM: Core & HTML, enhancement, P2)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
DUPLICATE
of bug 1471948
People
(Reporter: MattN, Unassigned)
References
Details
+++ This bug was initially created as a clone of Bug #1421070 +++
To enable us to start implementing browser UI with Custom Elements, the feature shouldn't be disabled for trusted documents when dom.webcomponents.customelements.enabled is false.
|
||
Comment 1•8 years ago
|
||
Just so I'm clear, this is being able to extend HTMLElement in a .html document loaded from chrome:// ? Not .xul or .xhtml documents?
Flags: needinfo?(MattN+bmo)
|
Reporter | |
Comment 2•8 years ago
|
||
(In reply to Dave Townsend [:mossop] from comment #1)
> Just so I'm clear, this is being able to extend HTMLElement in a .html
> document loaded from chrome:// ? Not .xul or .xhtml documents?
In my specific example, paymentRequest.xhtml, I want to extend HTMLElement in a .xhtml document loaded from resource://.
I don't think the HTML vs. XHTML distinction should matter though. We're only using DTD until we get Fluent over resource://
Flags: needinfo?(MattN+bmo)
|
|
||
Comment 3•8 years ago
|
||
.xhtml and .html use different parsers which might end up mattering.
|
||
Comment 4•7 years ago
|
||
Custom elements is enabled by default on release build (bug 1471948), do you think if we could close this bug?
Flags: needinfo?(MattN+bmo)
|
|
Reporter | |
Comment 5•7 years ago
|
||
Yes, thanks.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(MattN+bmo)
Resolution: --- → DUPLICATE
|
Assignee | |
Updated•7 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•