@Smylers:<br><br>So the whole rendering section is just for implementors and authors should act if no default style sheet is present or worse, if it could be everything, like a inline-block <div> or blue <table>, so that the author should set all supported properties to initial or the HTML5 "expected" value?<br>
That is:<br>I, author, want consistent rendering on all plaforms and browser: I import the HTML5 style sheet inside author ones.<br>I, implementor, want to provide backward-compatible rendering for those author that didn't follow rule 1), I import HTML5 style sheet inside UA defaults.<br>
In both case, a downloadable stylesheet would be much appreciated.<br><br>@Benjamin:<br><br>1) Ian initially said that they chose the binding property (instead of specifying appearance, border, color, etc.) in order to allow easy resetting of default look-and-feel for widgets<br>
2) I thought that author could make assumptions about the default CSS, Smylers convinced me that this cannot be true<br>3) at least in that case I know that if web site doesn't work, it is not my fault, but user's. But this has a major flaw: <br>
"customer is always right". In addition, once again, I was convinced that you can't make assumption on UA rendering.<br>4)<br>input[type=text] {<br>border:1px solid blue;<br>font: "Arial" 10pt;<br>
user-input: enabled;<br>user-modify: read-write;<br>cursor: url(I-beam.png);<br>}<br><br>looks different than<br><br>@appearance field {<br>border:1px solid ThreeDFace;<br>font:field;<br>user-input:enabled;<br>user-modify: read-write;<br>
cursor: text;<br>}<br>@sys-color ThreeDFace rgb(0,0,255);<br>@sys-font field {<br>font-family: "Arial";<br>font-size: 10pt;<br>}<br>@sys-cursor text {<br>src: url(I-beam.png);<br>}<br>input[type=text] {<br>appearance:field;<br>
}<br><br><p>assuming three imaginary at-rules to define UA skin at CSS level.</p><p>5) I agree with you, it may be impossible</p><p>6) either HTML5 defines everything, or it defines nothing</p><p>Giovanni</p>