Closed Bug 682728 Opened 13 years ago Closed 10 years ago

e10s: prompts are broken in content processes

Categories

(Toolkit :: General, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 899648
Tracking Status
e10s + ---

People

(Reporter: asaf, Unassigned)

Details

When a js alert is called from a content process, I get this error: Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIWindowWatcher.openWindow]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: file:///...nsPrompter.js :: openModalWindow :: line 416" data: no] That function (openModalWindow) gets the window-watcher service... for the current process, and then tries to attach a modal window its activeWindow property. In that context, activeWindow is, of course, null. I think we should fix this within the prompter. Window-watcher should not work in anything but the chrome process, imo. ? Questions: 1. Is there a js way to check if I'm running within the chrome process? 2. Is there a way to disallow getting a service in content processes
(In reply to Mano from comment #0) > 1. Is there a js way to check if I'm running within the chrome process? nsIXULRuntime.processType tells you what kind of process you're in.
(In reply to Mano from comment #0) > 2. Is there a way to disallow getting a service in content processes Only by changing the C++ XPCOM constructor to throw if created in the wrong process, I believe.
Assignee: mano → nobody
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.