Is there any way to be notified when a addon becomes compatible with FF 57?
i just installed 57 and as expected most of my addons aren't compatible. i'd like to know when they do become, or if they aren't going to be ported to work with 57. any way to be informed when they do become compatible or discontinued? thank
WHAT I CURRENTLY HAVE:
Adblock Plus Better Privacy Browsec Button Back Ciuvo Price Comparison Click%Clean Download Manager Tweak Eversync Flagfox Flashgot FVD Speed Dial Https Everywhere MEGA Metal Lion Australis Scrollbars II Navigational Sounds Redirect Bypasser Restart My Fox Save As PDF Status-4-Evar Stylish Tab Mix Plus Thumbnail Zoom Plus uBlock Origin/webext-hybird YesScript
Toate răspunsurile (9)
You need to go through your list of Extensions 1 by 1 and google them and find the Firefox Extension page for each and look to see if they are Firefox Version 57 compatible. This seems to work well if there is a Firefox 57 compatible Extension. Can use google search terms : Firefox Extension <old extension name> Comparable Note some Developers are still coding for 57 so only way to know is to go to each Developers page, possibly even email them if there is no info. Ask if them Other thing can do is go to The Firefox Extension page in Firefox and click the little gear upper right and send for update.
Oh.....mouse over stuff. Found that today and when moused over the Extension on the page said not compatible with my version.
Do remember, where there is a vacuum something will come along to fill it. Chrome add-ons are supposed to work with Firefox but I have no info, Again is compatibility and searching.
Please let us know if this solved your issue or if need further assistance.
Just FYI, you don't need both Adblock and uBlock, you should only have one. You should also check and see if there are updates for the rest of the add-ons, as many authors waited until today to publish their updates.
Which ones do not work in 57?
Tyler Downer said
Just FYI, you don't need both Adblock and uBlock, you should only have one. You should also check and see if there are updates for the rest of the add-ons, as many authors waited until today to publish their updates. Which ones do not work in 57?
yea one of the first things i plan is to check is if ublock plus adblock is out for 57, cause it works great in both chrome and opera.
"Chrome add-ons are supposed to work with Firefox but I have no info, Again is compatibility and searching."
i will check that out, but at this time i think ff still hasn't acted on this. shame it's supposedly been in the pipeline for a very long time.
Adblock and ublock both work with 57, and have for sometime. Only add-ons with "legacy" next to their name are not going to work in Firefox 57. and you should check for updates like I asid.
And chrome add-ons require the developer of the add-on to mark it compatible with Firefox. Very little work, but still a little
I am using 52 ESR, but I checked anyway.
Only a few of my accessibility extensions are compatible with 57+. Another few can't be made compatible with 57+; I don't know if webextensions would be able to do the same things. Most aren't compatible, at least yet.
I can't use the web without these accessibility tools, or others which do the same things.
Tyler Downer said
Just FYI, you don't need both Adblock and uBlock, you should only have one. You should also check and see if there are updates for the rest of the add-ons, as many authors waited until today to publish their updates. Which ones do not work in 57?
Interclue, Tab Mix Plus, IE Tab Plus no longer work. No Script (doesn't work like it used to). I had a few other add-ons that I can live without or that have replacements that I can live with, but the first 3 I mentioned were favorites of mine and I really miss them.
I've turned off automatic updates until enough time passes, then I will check again on a development computer to see if the plug-ins I use have ben revised for the new FireFox, until then -- I will be using the older version.
If the older version stops functioning, I will (sadly) switch to Chrome.
FYI, my plug-ins: