W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2011

Re: Firefox bug: "Worker" load ignores Content-Type version parameter

From: Julian Reschke <julian.reschke@gmx.de>
Date: Fri, 18 Nov 2011 12:52:36 +0100
Message-ID: <4EC64704.5070308@gmx.de>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
CC: Anne van Kesteren <annevk@opera.com>, www-archive@w3.org, public-Webapps@w3.org, Arthur Barstow <art.barstow@nokia.com>
On 2011-11-18 12:36, Julian Reschke wrote:
> On 2011-11-18 12:29, Bjoern Hoehrmann wrote:
>> * Anne van Kesteren wrote:
>>> On Fri, 18 Nov 2011 09:32:22 +0100, Julian
>>> Reschke<julian.reschke@gmx.de>
>>> wrote:
>>>> I recently started looking at FF's Content-Type related code. As far as
>>>> I can tell, there are at least two code paths, one taken for the HTTP
>>>> header field, one for HTML media type attributes. There may be more.
>>>>
>>>> The HTTP code definitively only processes the charset parameter.
>>>
>>> If Gecko does that for Workers, that would be a bug. Workers are UTF-8
>>> only.
>>
>> If you are saying that
>>
>> Content-Type: application/javascript;charset=iso-8859-1
>>
>> ... 0xC3 0xB6 ...
>>
>> should have U+00C3 U+00B6 when used via<script> and an U+00F6 when used
>> via `new Worker` then I will stand ready to roll over the floor laughing
>> when Firefox and Chrome are changed so they conform to this bizarre idea
>> instead of doing the right thing and treating the two cases the same.
>
> +1
>
> The only alternative would be to *reject* the script.
> ...

But it seems that this is what 
<http://dev.w3.org/html5/workers/#importing-scripts-and-libraries> says.

Please consider this a bug report.

Best regards, Julian
Received on Friday, 18 November 2011 11:53:14 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:48 GMT