Closed Bug 1471948 Opened 3 years ago Closed 3 years ago
Enable Custom Elements in release builds
No description provided.
Any specific reason why this depends on bug 1471947?
Because websites are broken if only custom elements or shadow DOM is enabled. They need to be both enabled or neither.
This was done in bug 1471947
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Documentation updates: Support notes updated in: https://developer.mozilla.org/en-US/docs/Web/Web_Components https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_custom_elements https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_shadow_DOM https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_templates_and_slots Note added to the Fx63 rel notes: https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/63#APIs I checked the compat data for each feature of the APIs, and some helpful person has already updated it all. Nice!
Actually, this still needs updating on https://platform-status.mozilla.org/#custom-elements and https://platform-status.mozilla.org/#shadow-dom. See https://github.com/mozilla/platform-status/pull/545 for details.
html5test.com still shows Custom elements as not supported even on today's 63.0b3.
html5test.com seems to be testing v0 Custom Element API. That is blink only API, not in any specification anymore.
(In reply to rniestroj from comment #6) > html5test.com still shows Custom elements as not supported even on today’s > 63.0b3. It will show up on https://html5test.com once they update to HTML5test version 9 (which is currently available at https://alpha.html5test.com/)
You need to log in before you can comment on or make changes to this bug.