- From: Richard Ishida <ishida@w3.org>
- Date: Tue, 07 Feb 2012 12:04:51 +0000
- To: Øyvind Stenhaug <oyvinds@opera.com>
- CC: www-style@w3.org
Fwiw, I just updated those test results while porting the tests to the W3C test framework. There were some changes to the results. See http://www.w3.org/International/tests/html-css/css-encoding/results-css-encoding RI On 07/02/2012 05:50, Richard Ishida wrote: > 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 12:07:29 UTC