Closed Bug 685320 Opened 13 years ago Closed 13 years ago

Components.classes["@mozilla.org/threads/workerfactory;1"] is undefined

Categories

(Core :: DOM: Core & HTML, defect)

8 Branch
defect
Not set
major

Tracking

()

RESOLVED WONTFIX

People

(Reporter: morac, Unassigned)

Details

(Keywords: regression)

According to the documentation, the nsIWorkerFactory component should exist and be scriptable from Firefox 4 through 9. See https://developer.mozilla.org/en/XPCOM_Interface_Reference/nsIWorkerFactory and https://developer.mozilla.org/en/Firefox_8_for_developers In the Aurora (Firefox 8) and later branches, Components.classes["@mozilla.org/threads/workerfactory;1"] is undefined so the following code throws an error: var workerFactory = Components.classes["@mozilla.org/threads/workerfactory;1"].createInstance(Components.interfaces.nsIWorkerFactory); It works in Firefox 4 through Beta (7). So basically ChromeWorkers are not available for use in JavaScript Modules in Firefox 8 and up.
We've already got a documentation request open to fix the docs, for now on you just do 'new ChromeWorker("myUrl.js");' from a JSM.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
Assignee: general → nobody
Component: JavaScript Engine → DOM
OS: Windows XP → All
QA Contact: general → general
Hardware: x86 → All
(In reply to ben turner [:bent] from comment #1) > We've already got a documentation request open to fix the docs, for now on > you just do 'new ChromeWorker("myUrl.js");' from a JSM. I actually tried that and Firefox crashed so I assume that wasn't working. It's possible I did something bad in the Worker, but I didn't crash under Firefox 7. https://crash-stats.mozilla.com/report/index/bp-3cab65b3-c592-4da2-b623-a89df2110907
(In reply to Michael Kraft [:morac] from comment #2) > https://crash-stats.mozilla.com/report/index/bp-3cab65b3-c592-4da2-b623- > a89df2110907 Hm, that's a bug, indeed. Let's file a new one for that?
I filed Bug 685916 for the crash.
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.