<br><br><div class="gmail_quote">2009/2/7 Benjamin Hawkes-Lewis <span dir="ltr"><<a href="mailto:bhawkeslewis@googlemail.com">bhawkeslewis@googlemail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On 7/2/09 14:22, Giovanni Campagna wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> 5) becss requires "one or more binding languages": it is not<br>
necessarily<br>
> XBL2, but currently XBL2 is the only one available: are you<br>
constraining<br>
> the implementation of HTML5 on that of XBL2?<br>
<br>
The rendering section has no actual requirements in it, so nothing is<br>
constrained. Furthermore, nothing requires the binding language used by<br>
the UA to actually be a real language, so long as it is triggered by the<br>
'binding' property.<br>
<br>
<br>
"A number of elements have their rendering defined in terms of the<br>
'binding' property" (HTML5, with normative reference to BECSS)<br>
No BECSS --> no rendering --> no interoperability<br>
</blockquote>
<br></div>
The introduction to the rendering section says:<br>
<br>
'User agents are not required present HTML documents in any particular way. However, this section provides a set of suggestions for rendering HTML documents that, if followed, are likely to lead to a user experience that closely resembles the experience intended by the documents' authors. So as to avoid confusion regarding the normativity of this section, RFC2119 terms have not been used. Instead, the term "expected" is used to indicate behavior that will lead to this experience.'<br>
<br>
<a href="http://www.whatwg.org/specs/web-apps/current-work/#rendering" target="_blank">http://www.whatwg.org/specs/web-apps/current-work/#rendering</a><br>
<br>
So the rendering section imposes *no* requirements on HTML5 conforming user agents, therefore the spec is not "constraining the implementation of HTML5 on that of XBL2".</blockquote><div><br>Yes, but UA that don't follow that set of CSS rules are not interoperable with UA that follow, ie scripts must detect what properties are ignored or defaulted.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <br>
<br>
Furthermore, user agents are free to use any method they like to mimic the suggested rendering, including CSS3 UI where applicable. They don't have to use BE CSS at all.</blockquote><div>They're "expected" to use CSS, and I expect that, according to html5, "button { binding: initial; }" makes it like a <span>.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
If this is not obvious from the text, perhaps you would like to suggest a change to the text that would make it clearer? </blockquote><div>I don't agree with rendering being "optional". If interoperability is so important (and it is), rendering should be normative. Obviously I'm not asking to depend on CSS, I'm asking that "UA should act if the following CSS was specified" (even if it doesn't support CSS)<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
--<br><font color="#888888">
Benjamin Hawkes-Lewis<br>
</font></blockquote></div><br>