2012-06-29 23:42, Ian Hickson wrote:
I consider all boilerplate to be a significant burden. I think there's a
huge win to making it trivial to create a Web page. Anything we require
makes it less trivial.
It's a win, but I'm not sure of the huge. When learning HTML, it's an
important aspect,
According to
http://www.whatwg.org/specs/web-apps/current-work/multipage/common-dom-interfaces.html#htmlpropertiescollection
*HTMLCollection* returns the first element.
*HTMLAllCollection* returns the first element or another HTMLAllCollection
if there are multiple elements
It's been pointed out to me that what I'm asking for is essentially the
same retargeting as we do for shadow DOMs in web components, where the
iframe is the shadow host and the document is the shadow root. This covers
all the details of what properties need to be updated when crossing the
document
On Fri, 13 Jul 2012, Ryosuke Niwa wrote:
According to
http://www.whatwg.org/specs/web-apps/current-work/multipage/common-dom-interfaces.html#htmlpropertiescollection
*HTMLCollection* returns the first element.
This is for compat in the default case, I believe.
*HTMLAllCollection* returns
On Fri, Jul 13, 2012 at 3:17 PM, Ian Hickson i...@hixie.ch wrote:
On Fri, 13 Jul 2012, Ryosuke Niwa wrote:
According to
http://www.whatwg.org/specs/web-apps/current-work/multipage/common-dom-interfaces.html#htmlpropertiescollection
*HTMLCollection* returns the first element.
This is
