W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2009

[whatwg] Text Encoding used to decode Web Worker's script.

From: Dmitry Titov <dimich@chromium.org>
Date: Thu, 19 Mar 2009 15:39:43 -0700
Message-ID: <28040fc60903191539m11f9a25p1d738d59d3e000fe@mail.gmail.com>
FYI: per IRC talk, the answer is the scripts should be using UTF-8 in
the absence of explicit override. Spec likely will reflect this more cleanly
at some point.

On Tue, Mar 17, 2009 at 11:57 AM, Dmitry Titov <dimich at chromium.org> wrote:

> Hi WHATWG!
> I can't find place in the spec which would define the text encoding used to
> decode the script of the Web Worker.
>
> For example, section 4.3.1, in "runnning a script", step 2, defines that
> for the <script> element - the encoding is 'inherited' from Document and can
> be overridden by 'charset' attribute or HTTP header.
>
> But for Workers, there is no specific instructions. I would assume
> (probably incorrectly) that the Web Workers behave like <script> element in
> this regard - so the encoding shoul dbe inherited from the 'parent
> Document', but this feels contradicting the specific requirements fro URLs
> in Workers to be encoded using UTF-8. It also feels the spirit of the
> Workers spec is leaning to UTF-8 everywhere :-)
>
> So in the absence of HTTP header, what text encoding should be used to
> decode the Worker scripts, including nested Workers and importScripts(...)
> targets?
>
> Thanks,
> Dmitry
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090319/a601fe0b/attachment.htm>
Received on Thursday, 19 March 2009 15:39:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 18:47:49 GMT