This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 23823 - Should the Worker and SharedWorker constructors resolve the URL using utf-8 (like WebSocket)?
Summary: Should the Worker and SharedWorker constructors resolve the URL using utf-8 (...
Status: RESOLVED DUPLICATE of bug 23822
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-14 04:48 UTC by contributor
Modified: 2014-01-16 17:15 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2013-11-14 04:48:01 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/
Multipage: http://www.whatwg.org/C#dedicated-workers-and-the-worker-interface
Complete: http://www.whatwg.org/c#dedicated-workers-and-the-worker-interface
Referrer: 

Comment:
Should the Worker and SharedWorker constructors resolve the URL using utf-8
(like WebSocket)?

Posted from: 59.37.57.226
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.26 Safari/537.36 OPR/18.0.1284.11 (Edition Next)
Comment 1 Ian 'Hixie' Hickson 2013-11-21 23:32:13 UTC 
Nah. WebSocket does it because it's a new protocol that uses UTF-8 throughout. Workers just use a regular HTTP GET.
Comment 2 Anne 2013-12-16 23:14:22 UTC 
Workers use utf-8 throughout as well. Also, the encoding override thing is a legacy thing. We shouldn't use it for new APIs.
Comment 3 Ian 'Hixie' Hickson 2014-01-15 22:56:40 UTC 
In a worker, sure, this API will use UTF-8. But this bug is about what happens outside the worker, in the document. See bug 23822.
Comment 4 Anne 2014-01-16 10:55:10 UTC 
Indeed, see bug 23822 comment 4 :-)
Comment 5 Ian 'Hixie' Hickson 2014-01-16 17:15:47 UTC 

*** This bug has been marked as a duplicate of bug 23822 ***