W3C home > Mailing lists > Public > www-svg@w3.org > September 2004

sXBL draft comments

From: Cameron McCormack <cam-www-svg@aka.mcc.id.au>
Date: Thu, 2 Sep 2004 13:15:09 +1000
To: www-svg@w3.org
Message-ID: <20040902031509.GA30345@mcc.id.au>

Some comments about the sXBL draft.

4.2 Processing content elements

Full XPath makes sense to me.  If you are already going to have XPath
support from DOM 3 XPath, you may as well use it.  What is a "predefined
XPath profile"?

But I guess it's the issue of dependency tracking that is the problem.
I have done it for full XPath, so it is possible.  (Well I didn't handle
the following and preceding axes, but who ever uses those. ;))

Regarding sorting, I hadn't really considered it.  I guess it is
certainly possible authors will want to sort the elements differently.
xsl:sort?  How close to XSLT do you want this template to become?

It is mentioned with the second proposal for handling content elements
which match no nodes that it keeps the flattened tree to be a superset
of the original DOM tree.  Why is that important?  If there are elements
which I don't want to include in the rendering, it seems silly that they
would have to be there with a display: none.  I vote for proposal 1.

6 DOM Interfaces

Will there be an interface for the xbl:content element as it appears in
the shadow tree?  Just like the SVGElementInstance interface.

6.1 The NodeXBL Interface

The element versions of firstChild, nextSibling etc. are nice.  It'll
save me writing little functions to skip over whitespace and comments.

6.2 The Event Interface

If you are worried about modifying Event from DOM Events, why not just
have a new interface (e.g. ForwardableEvent or something) and have all
of the events which are generated by SVG implement that interface too?

6.3 The XBLTemplateElement Interface

getElementById on XBLTemplateElement: good idea. :-)

About the note mentioning id attributes having to be of type ID, it
seems annoying that I would have to write some DTD just to allow my
custom elements to have id attributes that work with getElementById.
But I don't like DTDs anyway.

More comments later, perhaps!

Cameron

-- 
Cameron McCormack
|  Web: http://mcc.id.au/
|  ICQ: 26955922
Received on Thursday, 2 September 2004 03:15:17 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:14:55 UTC