Closed Bug 1187065 Opened 9 years ago Closed 8 years ago

[e10s] Ghostery addon does not show its resource:// pages (like options and walkthrough) in e10s

Categories

(Firefox :: Extension Compatibility, defect)

defect
Not set
normal

Tracking

()

RESOLVED INVALID
Tracking Status
e10s + ---

People

(Reporter: arenlor, Unassigned)

References

Details

(Keywords: addon-compat, Whiteboard: [e10s-top-addon] triaged)

+++ This bug was initially created as a clone of Bug #947030 +++ Method: 1. Install Ghostery addon: https://addons.mozilla.org/en-US/firefox/addon/ghostery/ 2. Attempt to view resource://firefox-at-ghostery-dot-com/ghostery/data/walkthrough.html in e10s window. Expected Result: View the walkthough. Actual Result: Blank page with nothing on it.
Summary: [e10s] Ghostery addon does not block tracking cookies with e10s → [e10s] Ghostery addon does not show walkthrough in e10s
No longer blocks: e10s-addon-exceptions
tracking-e10s: --- → ?
Keywords: addon-compat
Whiteboard: [e10s-top-addon]
Version: 41 Branch → unspecified
Status: UNCONFIRMED → NEW
Ever confirmed: true
As noted in the title of bug 1154407 (but not in its description), this seems a more general problem with resource:// URIs, affecting also Ghostery's options page, resource://firefox-at-ghostery-dot-com/ghostery/data/options.html
Summary: [e10s] Ghostery addon does not show walkthrough in e10s → [e10s] Ghostery addon does not show its resource:// pages (like options and walkthrough) in e10s
The console gives the following error message: not well-formed messages.js... :1:1 The messages.js links to: view-source:jar:file:///Users/jonny/Library/Application%20Support/Firefox/Profiles/nfdllrii.default/extensions/firefox@ghostery.com.xpi!/resources/ghostery/data/locales/en/messages.json If that helps anyone.
Whiteboard: [e10s-top-addon] → [e10s-top-addon] triaged
Ghostery is now a WebExtension and I don't think this bug is relevant anymore, please file a new bug if you are encountering bugs on a latest version.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.