Closed Bug 1171545 Opened 9 years ago Closed 7 years ago

"Fire IE (FireIE, Enhanced IE)" add-on does not work with e10s

Categories

(Firefox :: Extension Compatibility, defect)

41 Branch
x86_64
Windows 8
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: aenosedney, Unassigned)

References

Details

(Keywords: addon-compat)

https://github.com/yxl/Fire-IE/issues/128

FireIE being broken is the only remaining thing that prevents me from using e10s at work. Marking bug as 'blocker' because it literally is blocking me from using Aurora or Nightly at work.
Not a blocker.
Blocks: e10s-addons
Severity: blocker → normal
Keywords: addon-compat
Actually this is much higher severity than normal, critical at least. Most extensions are not as important because they do not provide core functions for the browser. Fire IE on the other hand is critical for many work websites at various companies worldwide for people who would otherwise be forced to use Internet Explorer. In my case, the website I'm using crashes in Internet Explorer, but does not crash in Firefox through Fire IE.

This extension should be considered to be moved to a separate bug report from the one you linked with a higher priority.

I would suggest the same for other high priority extensions that provide essential browser security such as adblock/noscript, except for the fact that ublock/umatrix exist and are already compatible with e10s and are in fact superior extensions.

The idea of bundling all extensions under 'normal' priority however does not seem very good.
With Firefox 57 only WebExtensions are permitted and are, by default, e10s compatible.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.