Tor and FF won't run together at the same time, going to have to post over at Torproject what they plan to do, have to stay with 6.5.2/6.2.5 whatever because upgrading that to 7.x.x caused it to lock or crash, again gotta post over there. However, already started to work with the resurrected K-Meleon that runs in 32-bit, Waterfox from the home page only runs in 64 bit, but K-Meleon doesn't need CTR either, though it may be trickier to use some of the ones I use daily like the Free Download Manager plug-in extension v.2.2.3, which I couldn't find today when I was trimming Tor with CTR to my taste. Notably, Waterfox has also stayed away from several of Mozilla's other poor choices, such as shipping a third-party extension (Pocket) in the browser as if it was part of it (Note: for those who want to use Pocket, it can be used in Waterfox if you install the old extension that used to be offered through AMO prior to Firefox bundling it in), and including "Sponsored Tiles" on the new-tab page, which may not sound too bad, but effectively means that third parties can pay Mozilla to let them see what sites you use with the excuse that they're doing it so they can show you sites you might like.Īlso Waterfox is planning some big infrastructure changes soon in order to separate itself from Firefox's issues and be able to stand on it's own as a true alternative to the likes of Firefox and Chrome.Īnother notable option is Pale Moon, (which also started out as a 64-bit build of Firefox before Mozilla offered a "Firefox" branded 64-bit Windows build) which will also not be discontinuing support for "legacy" addons, and (unlike Waterfox) didn't follow Mozilla's decision to switch to the "Australis" user interface Mozilla switched Firefox to in Firefox 29.Īlready received the upgrade to FFportable 55.0.1, so will I hurt any thing if I try to roll back to the 52ESR version? Unfortunately the outcry of Firefox users & Firefox extension developers have fallen on deaf ears at Mozilla, and they've recently moved forward with their plans by disabling "legacy" extension support in Firefox's "nightly" builds, and will surely continue to do so on all other builds of Firefox in the near future.įortunately however, there is a ray of hope in that Waterfox (started as a 64-bit build of Firefox, before Mozilla offered a "Firefox" branded 64-bit Windows build, which they still don't offer as the default download for 64-bit Windows users), which up to this point has kept up-to-date with most of Mozilla's changes, is not going to follow suit. These "legacy" extensions have been the proper method for creating Firefox extensions for years, and are still the only way to make an extension as complex as "DownThemAll!" or "Classic Theme Restorer".
Unfortunately Mozilla is shooting themselves in the foot by discontinuing Firefox's support for what they now term "legacy" extensions.
0 kommentar(er)
