3 ms·

You may want to check the detailed reports using the "Add-on Compatibility Reporter" extension. I found that the default indication is very conservative, and I

by yaantc 9y ago

You may want to check the detailed reports using the "Add-on Compatibility Reporter" extension. I found that the default indication is very conservative, and I used several extensions that were initially marked as not compatible, but actually worked well. So for the incompatible ones, particularly if they're rather niche (= not many people tried them with electrolysis), you may want to force multi-process and try them. And don't forget to make a report using the Reporter add-on, whether it went well or not ;)

toyg 9y ago
Thanks for the suggestions - I've now done them and it all looks ok with multiprocess forced.
- ionised 9y ago
  I have four addons that are apparently incompatible. How do you force multiprocess without disabling these addons?
  - toyg 9y ago
    Go to about:config and add the weirdly-named boolean "browser.tabs.remote.force-enable", set to true. Restart FF. Addons won't be disabled, but they might not work properly. If you see misbehaving extensions, install the Add-on Compatibility Reporter extension, then report by either: * going to the Addons/Extensions screen and clicking "Report Issue" near the misbehaving extension * clicking on the green puzzle piece now in your main toolbar, clicking on the X near the extension name, and then hitting the Submit button at the bottom. The latter will also send a report saying the other extensions are actually good, so I would do it only after making sure you've somewhat tested all of them. (All this was learnt today by insistent experimentation; the Addon Compat Reporter could do with some extra documentation or hints on what to do.)
    - ionised 9y ago
      I'm not seeing that boolean for some reason. I'm seeing; browser.tabs.remote.autostart browser.tabs.remote.desktopbehavior browser.tabs.remote.separateFileUriProcess but not the one you mentioned. I'm on Firefox Developer Edition 54.0b14 (64-bit) if that makes any difference.
      - toyg 9y ago
        It's not there by default, you must create it yourself. Right click on the list of option and select new -> boolean.

by yaantc 9y ago

toyg 9y ago

Thanks for the suggestions - I've now done them and it all looks ok with multiprocess forced.

ionised 9y ago
I have four addons that are apparently incompatible. How do you force multiprocess without disabling these addons?
- toyg 9y ago
  Go to about:config and add the weirdly-named boolean "browser.tabs.remote.force-enable", set to true. Restart FF. Addons won't be disabled, but they might not work properly. If you see misbehaving extensions, install the Add-on Compatibility Reporter extension, then report by either: * going to the Addons/Extensions screen and clicking "Report Issue" near the misbehaving extension * clicking on the green puzzle piece now in your main toolbar, clicking on the X near the extension name, and then hitting the Submit button at the bottom. The latter will also send a report saying the other extensions are actually good, so I would do it only after making sure you've somewhat tested all of them. (All this was learnt today by insistent experimentation; the Addon Compat Reporter could do with some extra documentation or hints on what to do.)
  - ionised 9y ago
    I'm not seeing that boolean for some reason. I'm seeing; browser.tabs.remote.autostart browser.tabs.remote.desktopbehavior browser.tabs.remote.separateFileUriProcess but not the one you mentioned. I'm on Firefox Developer Edition 54.0b14 (64-bit) if that makes any difference.
    - toyg 9y ago
      It's not there by default, you must create it yourself. Right click on the list of option and select new -> boolean.