This repository has been archived by the owner on Jul 30, 2019. It is now read-only.
Custom Elements - what to do with is="" attribute on regular elements #1277
Labels
Milestone
Comments
|
@brucelawson asked
Yeah, I think it would be prudent to mark it as "at risk". |
|
Leave this out, unless there is implementation in 2 browsers. (Doesn't seem to be in Chrome's implementation of v1 of web components, was in v0.) |
siusin
pushed a commit
that referenced
this issue
Apr 11, 2018
* initial pieces Chapters 2-3 normative stuff from the CE spec. Very WiP * cleaning up syntax Conversion to bikeshed/linking stuff. Possibly introducing some linking bugs to check when I'm mostly done :S * first pass syntax conversion This file will need another round of this, but leaving it for now. * Commit the element bits of custom elements Notes: Split autonomous and customized built-in elements a bit This commit includes is=, despite the resolution of #1277 It also presupposes that #1337 is resolved for the more restrictive approach. * at risk, is= in attributes table Add global/is to the attributes table Mark it, and customized built-ins, as under consideration for "at risk" * define is=, some editorial cleaning in global attributes section * update intro custom elements could be considered an extensibility mechanism... * some thank yous Certain to have missed people who deserved to be thanked. :( * thank yous * update changes split into the general piece and customized - if Firefox hasn't implemented them yet, they will be at risk for the 5.3 version. * fix syntax errors Bikeshed won't build without fixing some errors * Fix link * fix link again * link fix * update URN link * Fix link errors * linking fixes * Fix last link errors (of those introduced by this commit) * linking and grammar fixes Thank you @prlbr * tweaks fixing links, exporting definitions, hopefully fix multipage * fixes for review links, typos, ...
|
This is in fact implemented in both Firefox and Chrome, so #1343 includes it as part of custom elements. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Part of metabug #1229
Part of Custom Elements spec defines the ability to extend "real" HTML elements using the
is="foo-bar"attribute.is="foo-bar"attribute. On which elements is it allowed? Is it a global attribute?The text was updated successfully, but these errors were encountered: