Actually it's not only that the doctype is missing from http://people.ubuntu.com/~bryce/tmp/firefox-3-js-issue.html, but this page doesn't even have a root-element (should be a <html xmlns="http://www.w3.org/1999/xhtml">-tag in this case). http://people.ubuntu.com/~bryce/Plots/plots-0.7.html has a root-element, but it doesn't specify the xmlns, which probably causes <bar />- tags to be misinterpreted.
I have had the experience that a doctype is not absolutely necessary in most browsers, but nonetheless it's required by the W3C specification (http://www.w3.org/TR/xhtml11/conformance.html#s_conform).
I think it is relatively likely that this is caused by quirks-mode. I have often had cases (mostly in IE that doesn't really like XHTML) where <script /> tags spanned the whole rest of the document, which lead to empty pages and other interesting results.
Actually it's not only that the doctype is missing from http:// people. ubuntu. com/~bryce/ tmp/firefox- 3-js-issue. html, but this page doesn't even have a root-element (should be a <html xmlns="http:// www.w3. org/1999/ xhtml">-tag in this case). people. ubuntu. com/~bryce/ Plots/plots- 0.7.html has a root-element, but it doesn't specify the xmlns, which probably causes <bar />- tags to be misinterpreted. www.w3. org/TR/ xhtml11/ conformance. html#s_ conform).
http://
I have had the experience that a doctype is not absolutely necessary in most browsers, but nonetheless it's required by the W3C specification (http://
I think it is relatively likely that this is caused by quirks-mode. I have often had cases (mostly in IE that doesn't really like XHTML) where <script /> tags spanned the whole rest of the document, which lead to empty pages and other interesting results.