Closed Bug 1194942 Opened 9 years ago Closed 7 years ago

[e10s] DictionarySearch add-on doesn't display dictionary options in the context menu in e10s mode

Categories

(Firefox :: Extension Compatibility, defect)

42 Branch
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: mackeev, Unassigned)

References

()

Details

(Whiteboard: triaged)

User Agent: Mozilla/5.0 (Windows NT 6.3; rv:42.0) Gecko/20100101 Firefox/42.0 Build ID: 20150814004009 Steps to reproduce: The both above extensions are installed and configured. 1. Select a word and then press the right mouse button to select which dictionary to use. 2. Try to switch to the IE rendering engine by clicking the icon. Actual results: 1. no dictionary select options in the right-click menu 2. a blank page with a message "plug-in is disabled." Expected results: Expect to: 1. See dictionary options in the right-click menu 2. Switch rendering engine to IE Additional info: DictionarySearch functionality is back when I open the page in non-e10s window, but IE engine won't work even in this window (until I uncheck the multi-process box in Preferences.)
In general, it's one issue per bug, especially when both of these add-ons are probably very different. I will clone this for IE Tab v2.
Blocks: e10s-addons
Component: Untriaged → Extension Compatibility
Summary: FF 42 (dev) breaks DictionarySearch and IE Tab 2 extensions in multi-process mode → [e10s] DictionarySearch add-on doesn't display dictionary options in the context menu in e10s mode
I can confirm this - this addon, in the latest version available from AMO as of today (28.0.0.1-signed) doesn't add a context menu item when e10s is enabled. Gerv
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: [outreach needed] triaged
The developer has been notified.
Whiteboard: [outreach needed] triaged → triaged
With Firefox 57 only WebExtensions are permitted and are, by default, e10s compatible.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.