W3C home > Mailing lists > Public > www-style@w3.org > February 2012

Re: [CSS21] BOM vs HTTP charset

From: Richard Ishida <ishida@w3.org>
Date: Tue, 07 Feb 2012 05:50:19 +0000
Message-ID: <4F30BB9B.8090309@w3.org>
To: Øyvind Stenhaug <oyvinds@opera.com>
CC: www-style@w3.org
See 
http://www.w3.org/International/tests/html-css/css-encoding/results-css-encoding#precedence

RI

On 06/02/2012 17:15, Øyvind Stenhaug wrote:
> On Mon, 06 Feb 2012 15:02:42 +0100, Boris Zbarsky <bzbarsky@mit.edu> wrote:
>
>> On 2/6/12 8:43 AM, Øyvind Stenhaug wrote:
>>> According to a bug on the HTML5 spec, there are Web compatibility issues
>>> with the current encoding sniffing algorithm (where the HTTP charset
>>> parameter overrides a BOM).
>>>
>>> To maintain consistency, the CSS spec would need to change too.
>>
>> What do current CSS implementations do? It may well be that there are
>> web compat issues with having the same behavior in HTML and CSS here...
>
> As far as I can tell, WebKit ignores charset in the presence of a BOM,
> both for HTML and for CSS. IE9 treats them differently (seems to honor
> the charset for CSS).
>

-- 
Richard Ishida
Internationalization Activity Lead
W3C (World Wide Web Consortium)

http://www.w3.org/International/
http://rishida.net/
Received on Tuesday, 7 February 2012 05:53:01 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:50 GMT