[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 #26 from Daniel Buchner <danieljb2@gmail.com> ---
After someone piped up that the proposal to use <foo/bar>, was really intended
to mean foo[bar] (how developers *actually* write and refer to attributes on
the web), I thought I'd correct my own comment...then highlight that all the
problems from is="" would still apply, including a few additional issues -
here's rundown:

el.removeAttribute('x-foo') --> This does nothing - a lie via years of
developer inference on how the platform generally works

document.querySelector('x/x-foo') --> This throws an error - marking up
elements as custom elements in source becomes a one-off fudge, all other
interaction would require 'x[x-foo]'

Polyfills become ridiculous:

You would need to run logic on all *nodes detected* to inspect *all of their
attributes* for any that started with 'x-' to know to upgrade them - a
performance-destroying imposition

You'd need to wrap a litany of DOM methods and objects to block-and-throw when
the developer makes the *perfectly reasonable assumption* that they can remove
or add custom element boolean attributes - this includes removeAttribute,
NamedNodeMap methods, and a host of other interfaces.

In the end, it is all a tedious, largely irrelevant, exercise considering the
majority of components won't have a native tag they are semantically akin to.
This will manifest itself as: <x/x-foo></x>

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

Received on Wednesday, 9 January 2013 22:56:52 UTC