Firefox 57 Unbranded does not allow legacy extensions
20 posts
• Page 2 of 2 • 1, 2
Using an unbranded build of version 58, you can set extensions.legacy.enabled to true in about:config. This will enable legacy add-ons, but legacy APIs are constantly being removed, so your particular legacy add-ons may not function.
Dumby's hack broke in Fx 59. A CB user got a few legacy extensions working in Fx 59 by taking the defaults\preferences\*.js files in *.xpi files and placing these *.js files into the folder with the channel-prefs.js file. I got the Custom Buttons 0.0.5.8.9 fixed7pre and DOM Inspector Plus 2.0.17.1.2rc extensions working without Dumby's hack in Fx 58. I put the CB and DOMi Plus pref files into the folder with the channel-prefs.js file. I rather not use Dumby's hack in Fx 58 because it increases the startup time noticeably. I set these preferences.
Disabling e10s may affect what you might or might not get out of legacy extension...
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript
Buttons that can't be added by webextensions can be added by userChrome.js scripts. No noticeable impact on startup time that I've seen. ![]()
...and also - extensions.allow-non-mpc-extensions > true Metal Lion latest SeaMonkey & Thunderbird Themes - Sea Monkey and Silver Sea Monkey
"The only thing necessary for the triumph of evil, is for good men to do nothing." - Edmund Burke (attrib.)
20 posts
Page 2 of 2 • 1, 2
Who is onlineUsers browsing this forum: Mark12547 and 3 guests |
![]() |