Re: Null change proposal for ISSUE-88 (mark III)

Ian Hickson, Sun, 4 Apr 2010 01:01:53 +0000 (UTC):
 [...]

Since Maciej said he was willing to change Webkit to behave like 
Mozilla [1], just one more comment on the following:

> User agents vary in their handling of the Content-Language pragma. Some 
> user agents support a comma-separated list as meaning (contrary to the 
> intent of the Content-Language HTTP header)

I don't agree that it is contrary - it is just a different use, 
regardless of whether it contains one or many language tags. HTML4 
allows UAs to use the HTTP header (whether in the form of META or from 
the server) as fallback, but doesn't say what to dow when the header 
contains more than one language tag. The Mozilla behaviour is in 
principle perfectly acceptable.

> that the root element and its 
> descendants, in the absence of any lang="" attribute, are in multiple 
> languages. This seems to contradict the model expected by the :lang 
> selector and by the lang="" attribute, which assume that each element has 
> a single language.

OTOH, this is just a fallback/recovery solution. The most important 
problem that Mozilla browsers have w.r.t. both the content-language 
header and meta declaration, is that it doesn't respect the semantics 
of the empty string - neither when it comes to lang="<emptystring>" nor 
when it comes to content="<emptystring>". Whether the META 
content-language contains one ore several language tags doesn't matter 
in that regard.

[1] http://www.w3.org/mid/7FB03D6A-0A22-4DFF-B351-FB85CDCCA9EC@apple.com
-- 
leif halvard silli

Received on Wednesday, 7 April 2010 13:36:43 UTC