Re: State of subclassing and tag names in the component model

• From: Boris Zbarsky <bzbarsky@MIT.EDU>
• Date: Tue, 08 Nov 2011 12:50:14 -0500
• To: Dominic Cooney <dominicc@google.com>
• CC: public-webapps <public-webapps@w3.org>
• Message-ID: <4EB96BD6.5080501@mit.edu>

On 11/8/11 10:32 AM, Dominic Cooney wrote:
> There are two kinds of components—ones that are a refinement of
> something in HTML, like a select element or a button; and ones that have
> no genuine peer in HTML.
>
> This is the litmus test: If you were writing this today, would you start
> with a div or span? Then your component is probably the second kind.

Yes, agreed.

> Recalling the two kinds of components, I think custom tag names are a
> bad fit for the first kind—the kind that have a semantic cousin in HTML.
> A, B and C will be problems for these kinds of components.

Yes.

> I think the way forward is for us to work on components that use an
> existing tag name, and identify the component with an attribute, for
> now.

Sounds good.

-Boris

Received on Tuesday, 8 November 2011 17:50:43 UTC