W3C home > Mailing lists > Public > www-validator@w3.org > January 2004

Re: Empty <script> bug (XHTML documents) ->IE6 bug

From: Ian Hickson <ian@hixie.ch>
Date: Mon, 12 Jan 2004 18:10:20 +0000 (UTC)
To: Jim Ley <jim@jibbering.com>
Cc: www-validator@w3.org
Message-ID: <Pine.LNX.4.58.0401121805590.18121@dhalsim.dreamhost.com>

On Mon, 12 Jan 2004, Jim Ley wrote:
>>>> The HTML WG has stated that UAs should treat all text/html content as
>>>> legacy HTML content (aka Tag Soup):
>>>>
>>>>    http://lists.w3.org/Archives/Public/www-html/2000Sep/0024.html
>>>
>>> Unfortunately that's not what the specification says, if that's what
>>> they mean they need to clarify the specification, but then we know
>>> that already.
>>
>> Indeed, the specification doesn't say anything at all.
>>
>> What would you suggest UAs should do?
>
> Their best effort at understanding it

Obviously. I mean, what solution would you have here.


> that's always what I expect user agents to do, it's clearly broken, but
> it's the spec that's broken, any individual UA's error correction that
> get something meaningful is to be applauded, but equally those that
> don't can't be complained about too loudly.

What is wrong with the current behaviour, other than the fact that it
doesn't implement NET SHORTTAG?

Note that trying to parse <foo/> as an empty element breaks a large number
of sites that expect this to be treated the same as <foo>.

-- 
Ian Hickson                                      )\._.,--....,'``.    fL
U+1047E                                         /,   _.. \   _\  ;`._ ,.
http://index.hixie.ch/                         `._.-(,_..'--(,_..'`-.;.'
Received on Monday, 12 January 2004 13:12:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 25 April 2012 12:14:10 GMT