[Bug 18669] Switch from is= to <tag if a decision has been reached among implementers

https://www.w3.org/Bugs/Public/show_bug.cgi?id=18669

--- Comment #20 from Ian 'Hixie' Hickson <ian@hixie.ch> ---
IMHO the fallback element is more critical than the Web component. The
component is a way to augment an element with more power, but it's just a
variant of the fallback element.

To clarify, when I say "<input/foo>", I mean that's literally an <input>
element, with the "foo" component bound to it. It's tag name is "input". It
implements HTMLInputElement.

I'm fine with saying that the component can declare what element it's allowed
to be bound to, so that "<div/foo>" just fails to bind (same as "<div>").

Just having the fallback defined in the component is insufficient because it's
in the page that you need to know what kind of element it is, for fallback in
legacy UAs or non-Web-component UAs, for validation, for authoring sanity, for
semantic analysis, etc. Requiring that someone who's editing the page know how
all the components are defined is poor, IMHO.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 4 January 2013 22:50:40 UTC