Re: XBL2 as HTML5's extensibility mechanism (was Re: HTML 5 integration of SVG and MathML addresses ISSUE-33/mixedUIXMLNamespace-33?)

Robin Berjon <>, 2010-03-08 11:32 +0100:

> On Mar 3, 2010, at 21:19 , Dan Connolly wrote:
> > On Tue, 2009-11-17 at 13:15 +0000, Robin Berjon wrote:
> > [...]
> >> So, is there any reason why we can't just dub XBL2 as HTML5's
> >> extensibility mechanism and declare victory?
> > 
> > Is there a critical mass of support? Are implementors
> > happy to do their part in deploying it?
> It's hard to tell. Whenever I speak with implementers it's
> always on their TODO list, but somehow it never seems to reach
> maturity.

That seems like an accurate assessment to me also. Other work
seems to get higher priority, and plans for XBL2 implementation
get pushed down the stack.

> There certainly was a lot of support while the WebAPI
> WG was working on the draft. I won't presume to say why it is
> being delayed though — that might something to ask them within
> the HTML5 context.

I think the biggest reasons are that XBL2 is relatively large
piece of work to implement, and that there is a lot of other stuff
in HTML5 and WebApps --as well as from CSS and SVG specs -- that
browser projects have their potential XBL2 implementors working on.


Michael(tm) Smith

Received on Monday, 8 March 2010 12:19:57 UTC