WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
NEW
19913
"?" rhombi are shown instead of accentuated characters at some localized GMail log-in pages
https://bugs.webkit.org/show_bug.cgi?id=19913
Summary
"?" rhombi are shown instead of accentuated characters at some localized GMai...
Jeremy Bonan
Reported
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
.
Attachments
test case (with .htaccess)
(1.71 KB, application/zip)
2008-07-06 08:44 PDT
,
Alexey Proskuryakov
no flags
Details
View All
Add attachment
proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1
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.
Alexey Proskuryakov
Comment 2
2008-07-06 07:20:06 PDT
Interestingly, the page source does not have this problem.
Alexey Proskuryakov
Comment 3
2008-07-06 08:44:23 PDT
Created
attachment 22109
[details]
test case (with .htaccess)
Alexey Proskuryakov
Comment 4
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.
Alexey Proskuryakov
Comment 5
2008-07-06 08:46:55 PDT
<
rdar://problem/6056266
>
Alexey Proskuryakov
Comment 6
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.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug