OK, so it's a Yellow alert at the moment, when it turns Red, should we unplug, duck and cover ?
As of TODAY the legacy extensions still work in Nightly 57. Walt said that today's release was more like a re-brand. Rename.
I doubt that the warnings will turn red. Mine did not. They will just stop because the code that they use will be removed. Something you should see is that with Firefox 55 non e10s extensions are/should be disabled.
My suggestion? Look on AMO for replacements. Or? Learn to deal without them.
Me? I only had six to start. I found that three were available as Web-Ex. Two I found other solutions and one I just said 'oh heck' and moved on.
Grantius wrote:I vote for "Changes to Extensions in Firefox 57"
noticed i changed it to that
Cheers mate
Micro gaming box: AMD A10-7800 APU, 8gb RAM M350 ITX case (size of a book), Windows 10/Ubuntu Tablet/Laptop: Asus Transformer T100, Intel Atom 2GB RAM, Windows 10 x86 Mobile:Xiaomi Redmi Note 3 Pro
Putting it in my TODO list, unfortunately low priority because FlashGot still needs to go full e10s (NoScript got full priority for obvious reasons). [written Jun 30 2017]
I don't understand this phrase at all. WebExtensions are here, what's the point to port FlashGot to e10s?
Putting it in my TODO list, unfortunately low priority because FlashGot still needs to go full e10s (NoScript got full priority for obvious reasons). [written Jun 30 2017]
I don't understand this phrase at all. WebExtensions are here, what's the point to port FlashGot to e10s?
Maybe they mean Webextensions
Micro gaming box: AMD A10-7800 APU, 8gb RAM M350 ITX case (size of a book), Windows 10/Ubuntu Tablet/Laptop: Asus Transformer T100, Intel Atom 2GB RAM, Windows 10 x86 Mobile:Xiaomi Redmi Note 3 Pro
Putting it in my TODO list, unfortunately low priority because FlashGot still needs to go full e10s (NoScript got full priority for obvious reasons). [written Jun 30 2017]
I don't understand this phrase at all. WebExtensions are here, what's the point to port FlashGot to e10s?
Bah you can forget about flashgot for a long while. (Until noscript WE is complete and virtually trouble free) Even though it has 50% of the userbase of noscript it got 0% development time. Even though only some small bits (flashgot selection) were broken on e10s they went unfixed for years now.
lithopsian wrote:As of nightly 56 (exact date, anyone?), addons cannot be installed in e10s mode unless they are explicitly marked as compatible.
Just checked and they can't be installed at all, even with e10s turned off.
I'm guessing this means that there are no longer automatic CPOW shims for addons that don't do their own multiprocess handling?
Isn't that just controlled by "extensions.allow-non-mpc-extensions"? When I noticed non-mpc addons being disabled I just flipped that and they kept on working without an issue.
Inside Mozilla, CEO Chris Beard and his team are preparing to outmaneuver Google’s Chrome browser. The battle begins in November, with their release of Firefox 57.
lithopsian wrote:As of nightly 56 (exact date, anyone?), addons cannot be installed in e10s mode unless they are explicitly marked as compatible.
Just checked and they can't be installed at all, even with e10s turned off.
I'm guessing this means that there are no longer automatic CPOW shims for addons that don't do their own multiprocess handling?
Isn't that just controlled by "extensions.allow-non-mpc-extensions"? When I noticed non-mpc addons being disabled I just flipped that and they kept on working without an issue.
Probably, but it is a pretty strong statement that whatever you're doing just isn't supported any more.
mozillaZine is an independent Mozilla community and advocacy site. We're not affiliated or endorsed by the Mozilla Corporation but we love them just the same.
?
