|Summary:||"?" rhombi are shown instead of accentuated characters at some localized GMail log-in pages|
|Product:||WebKit||Reporter:||Jeremy Bonan <jeremybonan>|
|Component:||Page Loading||Assignee:||Nobody <webkit-unassigned>|
|Severity:||Normal||CC:||ap, eric, jchaffraix|
|Priority:||P2||Keywords:||GoogleBug, HasReduction, InRadar|
|Version:||528+ (Nightly build)|
|OS:||OS X 10.5|
Description Jeremy Bonan 2008-07-06 05:24:35 PDT
On the French login page of gmail, question mark rhombus are shown instead of any accentuated character é, è, ê, à, â. It has been so for a week (I'll pay more attention in the future) and is still the case with r35005.
Comment 1 Alexey Proskuryakov 2008-07-06 07:09:51 PDT
Confirmed with Safari 3.1.2 and with a local debug ToT, so this is not a WebKit regression, but something that changed on Google side. Steps to reproduce: 1. Log in to your GMail account normally. 2. In settings, change the language to French. 3. Log out. You are brought back to a login page, which has the problem. Re-opening doesn't resolve it. I also see this problem with Spanish, but not with Russian, Ukrainian, Polish, Czech or Catalan. It is not yet clear if this is a WebKit bug, but Firefox works correctly.
Comment 2 Alexey Proskuryakov 2008-07-06 07:20:06 PDT
Interestingly, the page source does not have this problem.
Comment 3 Alexey Proskuryakov 2008-07-06 08:44:23 PDT
Created attachment 22109 [details] test case (with .htaccess)
Comment 4 Alexey Proskuryakov 2008-07-06 08:45:56 PDT
It appears that Firefox has different behavior when seeing unknown charset for the main resource and for subresources. Fort the main resource, it ignores the unknown charset and uses the browser default encoding, while for subresources, it uses Latin-1. WebKit always ignores unknown encoding names (a comment in TextResourceDecoder.app says that it "helps some sites specifying invalid encodings"). We will need to find out what IE does to decide whether to match Firefox here. Regardless, this looks like more of a Google issue than a WebKit one.
Comment 6 Alexey Proskuryakov 2008-09-02 00:23:05 PDT
Can you still reproduce this? Looks like this was fixed on Google side. We'd still want to keep this bug open to consider the difference with Firefox though.