W3C home > Mailing lists > Public > public-html@w3.org > September 2008

Re: Unsupported transport-layer encodings

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 2 Sep 2008 07:35:59 +0000 (UTC)
To: Alexey Proskuryakov <ap@webkit.org>
Cc: Philip Taylor <pjt47@cam.ac.uk>, HTML WG <public-html@w3.org>
Message-ID: <Pine.LNX.4.62.0809020729360.7044@hixie.dreamhostps.com>

On Tue, 2 Sep 2008, Alexey Proskuryakov wrote:
> On Sep 2, 2008, at 8:50 AM, Ian Hickson wrote:
> > > 
> > > For WebKit, ignoring the unsupported encoding name worked well until 
> > > recently. But right now, some localizations of GMail are relying on 
> > > a bizarre Firefox quirk where unsupported charset names are treated 
> > > differently for main resource and for subresources: 
> > > <https://bugs.webkit.org/show_bug.cgi?id=19913
> > 
> > I couldn't reproduce this:
> > 
> >   http://www.hixie.ch/tests/adhoc/http/encoding/005-iframe.html
> 
> This tests a frame and its subframe, not a subresource (is my 
> terminology wrong?).

Like a style sheet? Those have their own rules for how to handle 
encodings, so that's out of scope of HTML5. Script encodings are defined 
in HTML5 and as defined ignore the HTTP headers altogether.


> Looks like GMail has changed, as I can no longer reproduce this issue 
> there.

Good. Then I shall ignore the issue for now. :-)

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 2 September 2008 07:35:58 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:38:58 UTC