<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BR><DIV><DIV>On Feb 15, 2006, at 4:41 PM, Ian Hickson wrote:</DIV><FONT class="Apple-style-span" face="Helvetica" size="3"><SPAN class="Apple-style-span" style="font-size: 12px;"><BR></SPAN></FONT><BLOCKQUOTE type="cite"><BLOCKQUOTE type="cite"><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">We're stuck with it forever as well, since most of the Dashboard widgets<SPAN class="Apple-converted-space"> </SPAN></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">use <script src="..."/> in HTML. You can say we're wrong in the spec,<SPAN class="Apple-converted-space"> </SPAN></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">but we won't be able to change it. :(</DIV></BLOCKQUOTE></BLOCKQUOTE><DIV><BR class="khtml-block-placeholder"></DIV><DIV>I think we need a dashboard mode, given that this is incompatible with all other browsers. I wonder if Mozilla changed it or if we were just confused about what it was doing. We can leave the dashboard mode just for HTML4 and ignore it for HTML5 doctype. In fact, all the widgets I found declare no doctype so dashboard mode can apply to quirks mode only.</DIV><BR><BLOCKQUOTE type="cite"><BLOCKQUOTE type="cite"> </BLOCKQUOTE><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">That, I'm afraid, is your problem. You may wish to consider having a<SPAN class="Apple-converted-space"> </SPAN></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">dashboard mode. <canvas>x</canvas> is also parsed differently in Safari<SPAN class="Apple-converted-space"> </SPAN></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">than in Mozilla and Opera; again, you may need a Dashboard parse mode if<SPAN class="Apple-converted-space"> </SPAN></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">you ever want to switch to the HTML5 way of parsing <canvas>. (Existing<SPAN class="Apple-converted-space"> </SPAN></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Web content has started relying on the HTML5 way.)</DIV></BLOCKQUOTE><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Requiring a close tag is technically better (for compatibility with browsers that don't support <canvas>). But it is somewhat frustrating to have to adapt to someone else's incompatible attempt to copy our feature.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>In any case we may as well start getting the system and example widgets changed, since in both cases the compatible syntax <script src="foo"></script> and <canvas></canvas> will work in WebKit. I'll file some bugs.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Regards,</DIV><DIV>Maciej</DIV><DIV><BR class="khtml-block-placeholder"></DIV></DIV></BODY></HTML>