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 <[email protected]> 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 > > >
