Open
Bug 1463033
Opened 6 years ago
Updated 2 years ago
Support of XHTML customized built-in element in XUL & XBL
Categories
(Core :: DOM: Core & HTML, enhancement, P3)
Core
DOM: Core & HTML
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox62 | --- | affected |
People
(Reporter: timdream, Unassigned)
References
Details
From identifying the call sites of NS_NewElement() I am pretty sure we will not be able to pick up [is] attributes from HTML elements in XUL document and XBL document: https://searchfox.org/mozilla-central/rev/8affe6e83188787eb61fe0528eeb6eef6081ba06/dom/xul/XULDocument.cpp#3286 https://searchfox.org/mozilla-central/rev/8affe6e83188787eb61fe0528eeb6eef6081ba06/dom/xbl/nsXBLPrototypeBinding.cpp#1307 I don't know if we need it though; so far we been talking about migrating XBL bindings to customized XUL elements, but not yet customized HTML elements. We could work on this when we need to.
Comment 1•6 years ago
|
||
Need to ensure we use the right prototypes - Custom (X)HTML element should be able to extend (X)HTML only and CE XUL only XUL elements.
Reporter | ||
Comment 2•6 years ago
|
||
(In reply to Olli Pettay [:smaug] from comment #1) > Need to ensure we use the right prototypes - Custom (X)HTML element should > be able to extend (X)HTML only and CE XUL only XUL elements. Would that simply throw with "Illegal Constructor" at runtime per spec? Do we need any more checks?
Updated•6 years ago
|
Priority: -- → P3
Reporter | ||
Comment 3•5 years ago
|
||
The HTML built-in element in XUL document case is fixed in bug 1512696. The XBL markup parsing is probably still broken.
Reporter | ||
Comment 4•5 years ago
|
||
Or perhaps this is already covered by bug 1462806 already? I am pretty confused. Regardless, if someone writes a test case to verify this it would be pretty great.
Comment 5•5 years ago
|
||
I don't think it's worth worrying about XBL. See bug 1397874.
Reporter | ||
Comment 6•5 years ago
|
||
(In reply to Alex Vincent [:WeirdAl] from comment #5)
I don't think it's worth worrying about XBL. See bug 1397874.
Yes, but we don't want to end up having to worry about not being able to convert a XUL element with XBL binding in XBL <content>
to a customized HTML built-in element, if we really need to.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•