23823 2013-11-14 04:48:01 +0000 Should the Worker and SharedWorker constructors resolve the URL using utf-8 (like WebSocket)? 2014-01-16 17:15:47 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED DUPLICATE 23822 http://www.whatwg.org/specs/web-apps/current-work/#dedicated-workers-and-the-worker-interface P3 normal Unsorted 1 contributor ian annevk ian mike contributor oldest_to_newest 96290 0 contributor 2013-11-14 04:48:01 +0000 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) 96675 1 ian 2013-11-21 23:32:13 +0000 Nah. WebSocket does it because it's a new protocol that uses UTF-8 throughout. Workers just use a regular HTTP GET. 97714 2 annevk 2013-12-16 23:14:22 +0000 Workers use utf-8 throughout as well. Also, the encoding override thing is a legacy thing. We shouldn't use it for new APIs. 98537 3 ian 2014-01-15 22:56:40 +0000 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. 98565 4 annevk 2014-01-16 10:55:10 +0000 Indeed, see bug 23822 comment 4 :-) 98630 5 ian 2014-01-16 17:15:47 +0000 *** This bug has been marked as a duplicate of bug 23822 ***