-
Notifications
You must be signed in to change notification settings - Fork 550
Conversation
Chapters 2-3 normative stuff from the CE spec. Very WiP
Conversion to bikeshed/linking stuff. Possibly introducing some linking bugs to check when I'm mostly done :S
This file will need another round of this, but leaving it for now.
Add global/is to the attributes table Mark it, and customized built-ins, as under consideration for "at risk"
some editorial cleaning in global attributes section
custom elements could be considered an extensibility mechanism...
Certain to have missed people who deserved to be thanked. :(
split into the general piece and customized - if Firefox hasn't implemented them yet, they will be at risk for the 5.3 version.
Bikeshed won't build without fixing some errors
sections/dom.include
Outdated
</li> | ||
|
||
<li>a <dfn id="when-defined-promise-map">when-defined promise map</dfn>, mapping <a>valid custom element names</a> | ||
to promises. It is used to implement the {{whenDefined}} method.</p> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
closing </p>
without opening?
sections/dom.include
Outdated
<a href="#custom-element">custom elements</a> are <a>defined</a>. In this example, | ||
we combine it with the <a>:defined</a> pseudo-class to hide a dynamically-loaded article's contents | ||
until all the <a>autonomous custom elements</a> it uses are defined.</p> | ||
<pre> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
note to update this to xmp
instead of pre
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
sections/dom.include
Outdated
|
||
<div class="example"> | ||
<p>This can occur due to reentrant invocation of this algorithm, as in the following example:</p> | ||
<pre> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pre
to xmp
so we don't have to escape <
and >
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done...
sections/dom.include
Outdated
super(); | ||
} | ||
} | ||
</pre> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
opened with an xmp
closed with a /pre
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
sections/dom.include
Outdated
const image = new AutoEmbiggenedImage(15, 20); | ||
console.assert(image.width === 150); | ||
console.assert(image.height === 200); | ||
</pre> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
closing /pre
but no opening
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
|
||
In addition, <a>custom element constructors</a> should implement the following good practices: | ||
|
||
<li> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
missing the opening ul
tag here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
(of those introduced by this commit)
<dd>Supplied by the element's author (inherits from {{HTMLElement}})</dd> | ||
</dl> | ||
|
||
An <a>autonomous custom element</a>'s' meaning is defined by its author. It <a>represents</a> its children. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There’s one '
too much.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yep
a <{tr}> already participates in the <a>table model</a>, | ||
and a <{input/checkbox}> has defined behaviour and participates in form submission. | ||
|
||
Since only existing table elements takes part in the <a>table model</a>, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo: the s
at the end of “takes” should not be there.
</li> | ||
|
||
<li> | ||
<p>They do not contain any <a>uppercase ASCII letters</a>, so user agent can always treat HTML elements ASCII-case-insensitively.</p> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it should be either “so the user agent can” or “so user agents can”.
|
||
<dt>A list of <dfn>observed attributes</dfn></dt> | ||
|
||
<dd>A <code>sequence<DOMString></code> that is a list of attribute names. When any of the named attributes changes value, the <code>attributeChangedCallback</code> <a>custom element reaction</a> is |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I’m not sure about this: Is the “s” at the end of “changes” in “When any of the named attributes changes value” correct? My feeling is that “any” goes with a plural here, so no “s” for the verb.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I went for "When any attribute in that list changes value"... since the callback runs once (and in my mind therefore singularly) for each such event.
Thank you @prlbr
sections/dom.include
Outdated
@@ -678,6 +679,993 @@ | |||
a linear transition of the element's prototype chain, from {{HTMLElement}} to a subclass, instead | |||
of a lateral one, from {{HTMLUnknownElement}} to an unrelated subclass.</p> | |||
|
|||
<!-- startCEinsert @@ --> | |||
<section> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove the <section>
tags outside.
sections/acknowledgements.include
Outdated
Ronald Eddy jr., | ||
Ryosuke Niwa, | ||
Sailesh Panchang, | ||
Scottt Miles, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/Scottt/Scott
::These are entirely author-defined, extending {{HTMLElement}} | ||
:<a>customized built-in Elements</a> | ||
::These extend elements that are already defined. <span class="note">This is typically to inherit some functionality.</span> | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there should be space after each ':
' or '::
';
@@ -2035,3 +2035,318 @@ | |||
and its flag reset. | |||
|
|||
</section> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ditto. Please remove these <section>
tags.
Otherwise looks good to me.
links, typos, ...
except for the example that uses |
This currently adds both autonomous custom elements, which are implemented in Webkit, Blink and Firefox, and customised built-in elements, apparently implemented in both Blink and Firefox.
See #1229, #1277 (This does currently include
is=
), #1337 (this PR restricts attributes todata-*
)This is pretty much ready for review, but not merge. It probably has linking errors, may have incomplete statements and other text bugs.
I will note the need for examples as a separate issue.