[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 #32 from Daniel Buchner <danieljb2@gmail.com> ---
(In reply to comment #31)
> This completely fails to address the concern I have, which is that the
> component element should be the fallback element and that if you can't not
> give the fallback ***(the binding just won't bind if there isn't the right
> fallback given)***

The binding ergonomics that you infer here are a massive head-fake for source
viewers, consumers of third-party components, and a whole host of other
potential users/viewers. The idea that the browser "just won't bind" is an
off-handed, let-them-eat-cake dismissal of all the monotonous, confusing,
fruitless, unintuitive annoyances it hoists upon developers.

Force-feeding one possible accessibility implementation in the face of other
(truly optional) options that also serve that use-case (see Brian's comment 29
above) at the expense of a superior product is trading a handknife for a
footgun. There are real, material issues introduced by using either is="" or
tag-escaped-attribute-fakery that person after person has called out and
opposed.

Let's be very clear about this: we are holding hostage a far more ergonomic API
that is relatively easy to polyfill, doesn't lie to developers or require deep
understanding of component mechanics/definitions to use, and is preferred ~10
to 1 by those on this thread (and other channels) who have weighed the options.

We should use the existing method Brian suggested, that the platform currently
supports, for declaring fallback content. It doesn't ram-rod a single, subset
concern on the rest of the system - that's a *benefit* in my book.

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

Received on Friday, 11 January 2013 01:18:08 UTC