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

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

From: Simon Pieters <simonp@opera.com>
Date: Fri, 18 Nov 2011 14:04:35 +0100
To: "Julian Reschke" <julian.reschke@gmx.de>
Cc: "Bjoern Hoehrmann" <derhoermi@gmx.net>, "Anne van Kesteren" <annevk@opera.com>, www-archive@w3.org, public-Webapps@w3.org, "Arthur Barstow" <art.barstow@nokia.com>
Message-ID: <op.v447xxdqidj3kv@simon-pieterss-macbook.local>
On Fri, 18 Nov 2011 13:46:16 +0100, Julian Reschke <julian.reschke@gmx.de>  

> That's fine if you use a new type, or profile an existing one.
> But claiming that charset=... means something else before depending on  
> the context it's used in is asking for trouble.

What kind of trouble?

>> Just use UTF-8. If you can't use UTF-8 in your workers, use ASCII and
>> character escapes. AFAIK there's have been no requests to support legacy
>> encodings in workers in Opera.
> I'm ok with that. I'm not ok with treating something that has a charset  
> of ISO-8859-1 silently as UTF-8, in particular when other parts of the  
> platform disagree.

Why not? We have context-dependent treatment of MIME types already (e.g. a  
text/html resource can be treated as a script).

Simon Pieters
Opera Software
Received on Friday, 18 November 2011 13:03:11 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:36 UTC