W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2011

State of subclassing and tag names in the component model

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Mon, 07 Nov 2011 16:29:59 -0500
Message-ID: <4EB84DD7.5070601@mit.edu>
To: public-webapps <public-webapps@w3.org>

At this I've lost track of what the current proposals are on tag names 
in the component model.  I've been thinking about this a bit, and I 
would like us to look at a particular use case: subclassing <img> and 
adding some behavior to it.

An obvious question: Should the localName/tagName of the resulting 
element be "img" or something else?

The way I see it, if it's "img" then everything should Just Work for 
this element and component binding just has to be done via an attribute.

If it's something else, then as far as I can tell we would probably need 
to change various specifications to look at whatever "img" is for this 
element (not the localName anymore).  This likely includes various parts 
of HTML5, possibly selector matching for UA and maybe user stylesheets, 
and so forth.  Furthermore, the result would still not be treated as an 
image by various script libraries out there.  But maybe that's desirable?

In any case, for every single place where one could consider what sort 
of element one has we would need to specify whether it's the localName 
that's being used or whatever other property evaluates to "img" or 
HTMLImageElement in this context.

Is that a reasonable summary of the state of things?

Received on Monday, 7 November 2011 21:30:28 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:36 UTC