No longer maintained (last version 5/2014). Part of the original functionality is meanwhile integrated with Firefox directly. Use Shift-F2 to open Developer Toolbar CLI, type restart, press enter. Smart Referer seems to be the better choice. Alternatives: Referer Control, but that one has privacy issues (loads 3rd party JS plus Disqus comments in iFrame, config page only) and lacks rule for "same domain" plus "from › to" connections. Looks like this won't be updated, as the corresponding issue has been closed without comment. WE ready, but rather limited as WEs cannot directly change FF settings.ĭevelopment stopped in 2013. Revert to the lousy support built-in to FF – and add In my Pocket – or switch to (self-hosted) Wallabag and use Wallabagger? Ready for XMas 2017 if not satisfied, partly solutions: Navigate Up + Wayback Helper / The Archiver / Archiver Menu Media Reload might have the former (video only?) ? FoxyImage offers parts of this (and adds other features), though "reload" and "search" seem to be missing. it only works with DeveloperTools being open (not even an icon without that), and can no longer validate Frames. As usual, the WE version is limited see feature comparison. Alternatives: ViolentMonkey, TamperMonkey, Custom Style Script Bookmarks Manager and Viewer claims to cover this. Partial Work-Around: Set findbar.modalHighlight and findbar.highlightAll to true in about:configĭeleted from AMO. It's fork Extension List Dumper 2 was last updated 1/2017, but isn't a WE either use about:support insteadĭead, and won't be updated anymore. Dev of Dorando says the same.ĭoesn't work anymore anyway, not updated since 2011. Is a replacement even possible? It's alternative Keybinder says here lack of corresponding APIs in WE make it impossible to maintain anymore. Looks like it stopped working with FF56 anyway. ? Probably no longer needed (see „Self Destructing Cookies“ below). None works on AMO pages, btw.ĭead, no further development (thanks, Mozilla). Will keep on working with Waterfox (see browser alternatives below).įormat Link is the only one that works (in the version released after ), and the dev gives excellent support. Not needed with 57+ anyway, as XUL is dead? Simple Add-On Manager includes the feature to disable compatibility checkĭead, no replacement (possible). Ready (alternative: uBlock Origin, see below)ĭead. Further, Flash is "click-to-play" now anyway, and FF kills Flash Cookies along with normal Cookies ( source?). When bold, considered a show-stopper (for me)Ĭan't be ported due to WE limitations. „X“: unavailable, no replacement (mostly none possible due to WE restrictions).„-“: unavailable and won't be created (comment might hold explanation and/or replacement).„√“: available/ready (at least seamingly, I've not tested them om FF57+ yet). The marks in the WE (WebExtension ready) column stand for: But first let's look where we stand (comments, additions and suggestions welcome): Addon compatibility/replacement overview Of course that's true, and having to re-configure ~80% of the browser of course lets me consider changing to a different browser (certainly not Chrome, though). I won't start a rant on „if I wanted a browser that looks like Chrome (Aurora with FF29), behaves like Chrome (only signed addons via a central store), and now feels like Chrome, I'd use Chrome“. So again, many of them are „jumping boat“, as they a) have no time to migrate to the new WebExtensions, b) WebExtensions don't offer the APIs required to perform the tasks needed by their addon, c) WebExtensions not even being ready yet (with just a couple of weeks left to the deadline, the API is still changing and far from being completed). Mozilla is doing it again: detering the addon developers who once made it „big“ (last time was when they forced them from XUL to their new „stable API“ for „long-time compatibility“ – which then proved to change as often as the XUL did before).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |