[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 #30 from Daniel Buchner <danieljb2@gmail.com> ---
> Is there any reason that someone could not achieve fallback in hixie's map
> example by simply developing their component so that the input was allowed
> to have the outer element?  In other words - if you wanted fallback - you
> could just:
> 
> <x-map>
>    <select name="country">
>        <option>FR</option>
>        <option>UK</option>
>        <option>US</option>
>    </select>
> </x-map>
> 
> Legacy browsers will show the x-map and presumably new system would upgrade
> on parse too... If so - what's the problem that the <select/map solves?

RIGHT ON!

This is a far better answer to this issue. In cases were the component's actual
optimal content is not inherently accessible, you could provide developers with
a 100% optional feature to streamline things just a bit more:

<x-map>
  <select fallback name="country">
      <option>FR</option>
      <option>UK</option>
      <option>US</option>
  </select>
</x-map>

If a developer used a fallback marker, the browser could skip tokenization of
those elements, which also conveniently removes the need for component authors
to bake code into their component definitions to deal with fallback content
that is unnecessary in their optimal render cases.

This is THE best solution that has been presented thus far, all the attribute
avenues have ***huge*** cons that are far more problematic than the issues they
solve (for the fractional-percentage cases they target).

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

Received on Thursday, 10 January 2013 20:00:35 UTC