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 24060 - Should importScripts always work? In browsers it does nothing if not called in the initial run
Summary: Should importScripts always work? In browsers it does nothing if not called i...
Status: RESOLVED INVALID
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-12-11 14:11 UTC by contributor
Modified: 2013-12-12 13:27 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2013-12-11 14:11:53 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/workers.html
Multipage: http://www.whatwg.org/C#dom-workerglobalscope-importscripts
Complete: http://www.whatwg.org/c#dom-workerglobalscope-importscripts
Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/

Comment:
Should importScripts always work? In browsers it does nothing if not called in
the initial run

Posted from: 90.230.218.37 by simonp@opera.com
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.48 Safari/537.36 OPR/18.0.1284.26 (Edition Next)
Comment 1 Ian 'Hixie' Hickson 2013-12-11 17:01:34 UTC 
why would it not always work?
Comment 2 Simon Pieters 2013-12-12 13:27:27 UTC 
I don't know. It doesn't. I take it that it should and it's a bug in the browsers.