- From: Cameron McCormack <cam@mcc.id.au>
- Date: Thu, 7 Dec 2006 20:44:40 +1000
- To: public-appformats@w3.org
Hi. This is a last call comment on the XBL 2 Editor’s Draft (dated 27 October 2006). 4.3 Attribute Forwarding ======================== …(A QName, such as value in the example above)… s/A/a/ In this section, there is one instance of the phrase “=-separated” with the “=” in orange, but the rest of the times it is black. This should be consistent. Changes to namespace prefix definitions in the shadow tree that affect QNames used in xbl:inherits attributes take effect the next time the attribute is parsed (which must be the next time the attribute is changed, but may be earlier). When is the earlier time that the attribute could be parsed? Of xbl:text: When used on the right-hand side, it indicates that any raw text nodes (including CDATA nodes) that are explicit children of the bound element should be coalesced and the resulting value should be stored as the attribute on the left-hand side. The term “coalesced” is not defined. Though I can guess what it means for text nodes, it should be defined (or use some more common term such as concatention in reference to the nodeValues). It also should mention if adjacency of these text nodes or whether they are element content whitespace affects this coalescing. “Raw” should also be defined wrt text nodes, or (better) just replaced with text that explicitly mentions exactly text and CDATA section nodes. Thanks, Cameron -- Cameron McCormack, http://mcc.id.au/ xmpp:heycam@jabber.org ▪ ICQ 26955922 ▪ MSN cam@mcc.id.au
Received on Thursday, 7 December 2006 10:36:51 UTC