Re: [XBL] Attribute Forwarding

On Thu, 7 Dec 2006, Cameron McCormack wrote:
> 
> 4.3 Attribute Forwarding
> ========================
> 
>   …(A QName, such as value in the example above)…
> 
> s/A/a/

Fixed.


> 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.

Fixed.


>   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?

Whenever the UA feels like it -- the sentence uses an RFC2119 term to 
allow earlier parsing.


> 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.

Fixed. Please let me know if it's better or not.



> “Raw” should also be defined wrt text nodes, or (better) just replaced
> with text that explicitly mentions exactly text and CDATA section nodes.

Removed "raw".

Cheers,
-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'