Skip to content

Commit

Permalink
Explicitly state “is” attribute conformance requirements
Browse files Browse the repository at this point in the history
  • Loading branch information
sideshowbarker authored and domenic committed Dec 16, 2016
1 parent 1d3dd5d commit 43ab125
Showing 1 changed file with 3 additions and 2 deletions.
5 changes: 3 additions & 2 deletions source
Expand Up @@ -65843,10 +65843,11 @@ console.log(plasticButton2.getAttribute("is")); // will output "plastic-button"<
<span data-x="concept-custom-element-definition-name">defined name</span>.</p></li>

<li><p>A <dfn data-export="">customized built-in element</dfn>, which is defined with an <code
data-x="">extends</code> option. These types of custom elements have local name equal to the
data-x="">extends</code> option. These types of custom elements have a local name equal to the
value passed in their <code data-x="">extends</code> option, and their <span
data-x="concept-custom-element-definition-name">defined name</span> is used as the value of the
<dfn><code data-x="attr-is">is</code></dfn> attribute.</p></li>
<dfn><code data-x="attr-is">is</code></dfn> attribute, which therefore must be a <span>valid
custom element name</span>.</p></li>

</ol>

Expand Down

0 comments on commit 43ab125

Please sign in to comment.