[Webkit-unassigned] [Bug 24473] RTL: haaretz.co.il - wrong charset in HTTP headers (csISOLatinHebrew instead of Windows-1255) leading to a mirrored rendering

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=24473





------- Comment #8 from jshin at chromium.org  2009-05-07 11:58 PDT -------
First of all, my comment in mozilla bugzilla at
https://bugzilla.mozilla.org/show_bug.cgi?id=308187#c20 is wrong. When I wrote
that, I thought IE puts a higher precedence on meta than on http (I had seen so
many pages with conflicting http charset and meta charset with meta being
correct that only worked in IE. I don't know how now). It turned out that it
does not. So, Uri's comment at
https://bugzilla.mozilla.org/show_bug.cgi?id=308187#c17 is right on. 

As for being a bug compatible with IE by choking on quotation marks in charset
param of C-T header fields, I don't feel very comfortable with that. There's a
possibility that we may break some web sites that we don't currently break.
Sure, they're also broken in IE, but do we want that?  A hypothetical case
(perhaps a rare case) is as following:

1. The default charset of a browser is set to, say, GBK
2. A user visits a page which emits the following HTTP header field:

Content-Type: text/html; charset="EUC-KR"

And, there's no meta charset declaration but the page is encoded in EUC-KR.

3. Webkit and Firefox interpret the page correctly as in EUC-KR

4. IE interprets it as GBK (the default charset). 

IE can get away with this because the majority of visitors to the site are
Koreans and their default encoding is set to EUC-KR. 

So, although I'm kinda annoyed by haaretz.co.il's failure/refusal? to fix their
bug for so many years, I'm inclined toward special casing it (and hopefully
only a few other). 





-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.