W3C home > Mailing lists > Public > www-validator@w3.org > November 2011

Re: [VE][247] Add Subject Here

From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Wed, 16 Nov 2011 17:49:46 +0100
To: Philip TAYLOR <P.Taylor@Rhul.Ac.Uk>
Cc: www-validator@w3.org
Message-ID: <20111116174946848836.1f0cc876@xn--mlform-iua.no>
Philip TAYLOR, Wed, 16 Nov 2011 16:23:53 +0000:

> If the validator were to stop issuing the warning, and an HTML 
> 4.01-compliant browser were to start treating the ">" as character
> data (as it should), how would the poor user be able to identify
> the cause ?

A quite hypothetical 'if'.

> An HTML 4.01 document, with an HTML 4.01 DOCTYPE, is not,
> and never will be, subject to HTML 5's rules.

Agree. But, why does the validator say: «For HTML 4.01 Strict, the '/' 
terminates the tag <FOO (with an implied '>')» ? It sounds as if '/>' 
is handled differently - per the DTD - with the Strict DTD compared to 
with the Transitional DTD. Is that the case?

If it is the case, then is must be the case that the '/' has zero 
effect with the Transitional DTD, but that it *has* effect with the 
Strict DTD. In which case the message is wrong, for the Transitional 
DTD.

>> But even per HTML4's rules,  it is only a warning and not
>> an error.
> 
> In this case, yes, because it occurs within an <img> tag
> within the body; but if it were a <meta ... /> in the <head>
> region ?  What then ?

Meta elements with a '/>' is not a problem to today's HTML browser - if 
it ever was.
-- 
Leif H Silli
Received on Wednesday, 16 November 2011 16:50:23 GMT

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