W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2011

Re: HTMLElement.register--giving components tag names

From: Ian Hickson <ian@hixie.ch>
Date: Sun, 4 Sep 2011 03:20:53 +0000 (UTC)
To: Dominic Cooney <dominicc@chromium.org>
cc: WebApps WG <public-webapps@w3.org>
Message-ID: <Pine.LNX.4.64.1109040316380.15282@ps20323.dreamhostps.com>
On Sat, 3 Sep 2011, Dominic Cooney wrote:
> > 
> > I think the XBL approach is far superior here -- have authors use 
> > existing elements, and use XBL to augment them. For example, if you 
> > want the user to select a country from a map, you can use a <select> 
> > with a list of countries in <option> elements in the markup, but then 
> > use CSS/XBL to bind that <select> to a "component" that instead makes 
> > the <select> look like a map, with all the interactivity that implies.
> 
> That sounds appealing, but it looks really hard to implement from where 
> we right now.

I don't think "it's hard" is a good reason to adopt an inferior solution, 
especially given that this is something that will dramatically impact the 
Web for decades to come.

XBL already has multiple implementations in various forms. I certainly 
agree that we should adjust XBL2 to take into account lessons we have 
learnt over the past five years, such as dropping namespaces and merging 
it into HTML instead of forcing an XML language on authors, but taking a 
significantly less capable solution simply because XBL is difficult seems 
like a very poor trade-off.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Sunday, 4 September 2011 03:22:45 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:47 GMT