Closed Bug 1368803 Opened 7 years ago Closed 7 years ago

Non-MPC extensions should not be disabled if e10s is disabled

Categories

(Toolkit :: Add-ons Manager, defect, P5)

Product:
Toolkit
Component:
Add-ons Manager
Version:
55 Branch
Platform:
x86
Windows 10
Type:
defect

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: alice0775, Unassigned)

Details

(Keywords: regression, Whiteboard: triaged)

Attachments

(1 file)

bug.png
66.19 KB, image/png
Details 
Firefox52esr works without problem.


Reproducible: always

Steps To Reproduce:
1. Make sure e10s is disabled
2. Install e10s incompatible legacy addon such as "DOM Inspector"


Actual Results:
The addon is automatically disabled.
No Restart now button display.

Expected Results:
A Restart now button should display.
Attached image bug.png — 

    
    

    
  
You can work around this by flipping the preference extensions.allow-non-mpc-extensions.
Given that this only affects Nightly and it will change significantly in 57, this isn't a high priority.
Priority: -- → P5
Summary: E10s incompatible legacy addon is automatically disabled when newly install it even if  e10s had been disabled → Non-MPC extensions should not be disabled if e10s is disabled
Whiteboard: triaged

    
    

    
  
Neither non-e10s Firefox nor non-multiprocessCompatible extensions are things we can spend any time on supporting.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX

          You need to log in
          before you can comment on or make changes to this bug.
        






  

    
  







  

    

      
Attachment

      

      
      
      
      
    

    

      

        

          

            
General

            

              Creator: 



            

            
Created: 

            
Updated: 

            
Size: