Closed
Bug 547444
Opened 15 years ago
Closed 15 years ago
[E10s] Can not access xulapp chrome url using content process event handlers
Categories
(Core :: IPC, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 542907
People
(Reporter: dougt, Unassigned)
Details
Fennec wants to use content process event handlers to forward content events to chrome. In our code we do something like:
messageManager.loadFrameScript("chrome://browser/content/fennec-content.js", true);
The content of fennec-content.js simply has one dump statement.
When using IPC, we do not see the dump statement, but instead we see an error message on the console that says:
Couldn't convert chrome URL: chrome://browser/content/fennec-content.js
The error is from here:
http://mxr.mozilla.org/mozilla-central/source/chrome/src/nsChromeProtocolHandler.cpp#196
We then added this file as an inline script to our main xul file -- just to see if we added it properly to the jar.mn. We re-ran, and saw the dump without any error.
Updated•15 years ago
|
Summary: Can not access xulapp chrome url using content process event handlers → [E10s] Can not access xulapp chrome url using content process event handlers
Updated•15 years ago
|
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•