Re: Unsupported transport-layer encodings

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?). We have a reduction attached to <https://bugs.webkit.org/show_bug.cgi?id=19913 
 >.

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

- WBR, Alexey Proskuryakov