Comments on: Firefox 3 CSS and HTML support information available http://www.webdevout.net/tidings/2008/06/16/firefox-3-css-and-html-support-information-available/ Updates on the march of progress. A weblog about web design, standards, web browsers, and the overall health of the Web. Wed, 14 Dec 2011 14:45:24 +0000 http://wordpress.org/?v=2.8.4 hourly 1 By: Steuard http://www.webdevout.net/tidings/2008/06/16/firefox-3-css-and-html-support-information-available/comment-page-1/#comment-4099 Steuard Thu, 26 Jun 2008 17:08:18 +0000 http://www.webdevout.net/tidings/2008/06/16/firefox-3-css-and-html-support-information-available/#comment-4099 The <code>title</code> formatting issue (allowing authors to manually specify line breaks using character entities) in Firefox seems to be challenging to solve. My understanding at the moment is that major changes to the basic structure of Gecko's parser would be necessary to fix this (or perhaps a tremendously ugly hack). That's not to say that it won't happen, but it's an intimidating prospect (and it may well be too deep a change to accept until the next major version change: <em>after</em> Firefox 3.x). But unfortunately, I think we're stuck with the "strip newlines entirely" behavior based on the HTML spec. It's spelled out pretty explicitly there. I quoted (and linked) the relevant bits when filing the <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=358452">currently active Bugzilla bug</a> on this issue. The discussion in that bug (and the ones it links to) may give you some idea of the issues involved if you're interested. The title formatting issue (allowing authors to manually specify line breaks using character entities) in Firefox seems to be challenging to solve. My understanding at the moment is that major changes to the basic structure of Gecko’s parser would be necessary to fix this (or perhaps a tremendously ugly hack). That’s not to say that it won’t happen, but it’s an intimidating prospect (and it may well be too deep a change to accept until the next major version change: after Firefox 3.x).

But unfortunately, I think we’re stuck with the “strip newlines entirely” behavior based on the HTML spec. It’s spelled out pretty explicitly there. I quoted (and linked) the relevant bits when filing the currently active Bugzilla bug on this issue. The discussion in that bug (and the ones it links to) may give you some idea of the issues involved if you’re interested.

Posted using Mozilla Firefox 3.0 on Windows.

]]> By: Daniel http://www.webdevout.net/tidings/2008/06/16/firefox-3-css-and-html-support-information-available/comment-page-1/#comment-4097 Daniel Sun, 22 Jun 2008 13:11:58 +0000 http://www.webdevout.net/tidings/2008/06/16/firefox-3-css-and-html-support-information-available/#comment-4097 That's great data already, thanks. Even if HTML5 isn't anywhere near Candidate Recommendation, it defines a small edge case your tables treat as error: Expanded form of empty attributes. Currently Gecko, WebKit and the latest Presto (Kestrel, Opera 9.5) represent as readonly="" (DOM and CSS). Trident says it's readonly="true" (CSS only knows [readonly]). Accroding to HTML5, the epmty readonly attribute becomes readonly="" and stays with the empty string. As said, this is true for every engine but IE. So I think your tables should treat readonly="" as pass. As well as the IE7 mass testcase which tests for this case. That’s great data already, thanks.

Even if HTML5 isn’t anywhere near Candidate Recommendation, it defines a small edge case your tables treat as error: Expanded form of empty attributes.

Currently Gecko, WebKit and the latest Presto (Kestrel, Opera 9.5) represent as readonly=”" (DOM and CSS). Trident says it’s readonly=”true” (CSS only knows [readonly]).

Accroding to HTML5, the epmty readonly attribute becomes readonly=”" and stays with the empty string.

As said, this is true for every engine but IE. So I think your tables should treat readonly=”" as pass. As well as the IE7 mass testcase which tests for this case.

Posted using Mozilla Firefox 3.0 on Windows.

]]>