Closed Bug 1165916 Opened 9 years ago Closed 9 years ago

"DOM Inspector" add-on does not work with e10s

Categories

(Firefox :: Extension Compatibility, defect)

41 Branch
x86
macOS
defect
Not set
normal

Tracking

()

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

People

(Reporter: husseydevin, Unassigned, NeedInfo)

References

Details

Does not work on remote pages, but works on local pages (like chrome://browser/content/browser.xul or about:addons)

Menu option or Element Inspector Shift+Right Click do not work at all. Do nothing.

Shift-RC console message: 
TypeError: 'stopPropagation' called on an object that does not implement interface Event.   
 (3) RemoteAddonsParent.jsm:574:0

Menu option console message:
TypeError: content is null
 browser.xul:1:0
Blocks: e10s-addons
KaiRo, who is the dev contact for the SeaMonkey Council's add-ons?

https://addons.mozilla.org/en-US/firefox/user/seamonkey-council/
tracking-e10s: --- → +
Flags: needinfo?(kairo)
I'll forward this to Philip, I think he has done some of the recent patches to DOMi and he's the add-ons guru in the SeaMonkey team.
Flags: needinfo?(kairo) → needinfo?(philip.chee)
And BTW, I can confirm that it doesn't even start up in Firefox Nightly with e10s enabled, as I am using it for my theme design work in many cases.
Status: UNCONFIRMED → NEW
Ever confirmed: true
I'm familiar with DOMi but not so much with e10s.
I guess I need to talk to someone in the devtools team.
(In reply to Robert Kaiser (:kairo@mozilla.com) from comment #3)
> And BTW, I can confirm that it doesn't even start up in Firefox Nightly with
> e10s enabled, as I am using it for my theme design work in many cases.

You can still inspect the chrome:// or about: URLs, as they run in the UI and not e10s. This includes the latest update (2.0.15.1-signed) that just came out. At least for me.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.