- From: Cameron McCormack <cam@mcc.id.au>
- Date: Thu, 7 Dec 2006 20:34:41 +1000
- To: public-appformats@w3.org
Hi. This is a last call comment on the XBL 2 Editor’s Draft (dated 27 October 2006). 2 XBL Elements ============== When an XBL element is found inside an element other than those listed under the “Expected contexts” list in the definitions below, it is in error. When an XBL element has a child node that does not satisfy the “Expected children” list in its definition (for instance because it is the wrong node type, wrong element type, or because too many elements of its type preceded it), the child is in error. In both cases, being in error means that the UA must, for the purposes of XBL evaluation, treat the XBL subtree as it would if the erroneous node and all its descendants were not present in the DOM. Is this subtree in error? <xbl:xbl> <!-- A comment --> </xbl:xbl> since the “Expected children” list for the xbl element does not list comment nodes? What about whitespace-only text nodes? XBL user agents that do not support CSS should not render the XBL elements other than the div element, which they should render as a paragraph-like element. What about UAs that support CSS but not the box model, for example an SVG-only UA? What does a paragraph-like element mean for them? 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:26:59 UTC