Henri Sivonen wrote:
On Jan 23, 2006, at 18:43, dolphinling wrote:
Second, it could force authoring tools to produce invalid documents
if the author did not provide any alt text. However, those documents
would be non-conformant anyway, so this is not a huge problem.
It is. Authoring
On Jan 24, 2006, at 13:06, dolphinling wrote:
File - Save
If you save this page as is, it will be non-valid for the
following reasons:
You did not specify alternate text for one or more images.
The page will display properly, but will be less accessible to some
users and will fail
On 24 Jan, 2006, at 5:43 AM, dolphinling wrote:
Matthew Paul Thomas wrote:
Bizarre but serious conclusion: alt= should be optional for img in
documents where a meta name=generator... element is present.
How about Authoring tools MUST only provide alternate text that the
author explicitly
On Tue, 24 Jan 2006, Lachlan Hunt wrote:
As for how to parse it, I'll use these test cases to demonstrate what I
consider to be the most sane way to handle comments. (Assume EOF at the
end of each one)
Test Case | Comment Content | Output
Ian Hickson wrote:
On Tue, 24 Jan 2006, Lachlan Hunt wrote:
PA!- !--SS -- | - ! | PASS --
Comment should be - !-- IMHO. It's still a bogus comment (in HTML5
nomenclature), the -- part is irrelevant.
Ok, so if a comment only starts with '!' then it ends at
On Wed, 25 Jan 2006, Lachlan Hunt wrote:
Ian Hickson wrote:
On Tue, 24 Jan 2006, Lachlan Hunt wrote:
PA!- !--SS -- | - ! | PASS --
Comment should be - !-- IMHO. It's still a bogus comment (in HTML5
nomenclature), the -- part is irrelevant.
Ok, so
Ian Hickson wrote:
On Wed, 25 Jan 2006, Lachlan Hunt wrote:
Ian Hickson wrote:
On Tue, 24 Jan 2006, Lachlan Hunt wrote:
PA!-- FAIL -- SS | FAIL| PASS
Disagree. The terminator should be --, not -- S* . I don't see any
good reason to have -- S* .
I was working
Ian Hickson wrote:
On Wed, 25 Jan 2006, Lachlan Hunt wrote:
I tested the following in the live dom viewer using Firefox 1.5.0.1 Win
and Mac, Opera 8.5/Mac, Opera 9 Win and Mac, Safari 2.0.3, IE6, OmniWeb
5.1.2 and iCab 3.0.1.
!DOCTYPE html
PA!-- FAIL -- SS
This triggers SGML comment
On Wed, 25 Jan 2006, Lachlan Hunt wrote:
Ian Hickson wrote:
On Wed, 25 Jan 2006, Lachlan Hunt wrote:
I tested the following in the live dom viewer using Firefox 1.5.0.1 Win
and Mac, Opera 8.5/Mac, Opera 9 Win and Mac, Safari 2.0.3, IE6, OmniWeb
5.1.2 and iCab 3.0.1.
!DOCTYPE
Quoting Lachlan Hunt [EMAIL PROTECTED]:
This entire discussion started from the developers of all the
browsers who implemented the SGML comment mode coming to me and
telling me I was stupid for even suggesting that this is how
comments should be parsed. The whole point of all this is to
Also sprach Ian Hickson:
This triggers SGML comment parsing mode (which you don't want to be
testing)
in a number of browsers.
Why? The closer we can define the behaviour to be compatible with existing
standards mode behaviours, the better it will be for backwards
It will be great to see OBJECT handling clarified. Here are some
points:
On encountering an OBJECT, the UA must check type and/or classid.
If the type attribute identifies a file type the UA handles
internally, check if the OBJECT has a data attribute. Render contents
of this attribute if
12 matches
Mail list logo