Flagfox 6.1.2 and 5.2.10 updates released

Flagfox 6.1.2 for Firefox 60+ has been released and is available for update and download from AMO. Flagfox 5.2.10 has also been released for Firefox 52 ESR, SeaMonkey, and Firefox forks based on older Gecko versions (or at least anything newer than Firefox 24). You can download it here.

Flagfox 6.1.2 changelog:

  • IPv4 & IPv6 address location database updates for August 2018
  • Added DNS cache check retries if no IP is found within a minute of startup (for already loaded tabs)
  • Created a hack to allow hiding of menus without deletion+recreation (WebExt API can only disable)
  • Flagfox menus now hide automatically for all URLs which never show Flagfox icons (e.g. about:newtab)
  • Flagfox menus are now generated on first open instead of all at first startup (using new APIs more)
  • More cleanups and optimizations

Flagfox 5.2.10 changelog:

  • IPv4 & IPv6 address location database updates for August 2018

This release was delayed a little bit this month for more testing of the menus revamp and startup DNS handling. No real user-facing changes here beyond working better, so still just counting this as a minor update. As per usual, contact me if something explodes.

Mozilla ends support for Firefox 52 ESR next month and thus the Flagfox 5.2.11 ESR update will be the final one on the old branch. Update to Firefox 60 ESR and Flagfox 6.1.x within the next couple months.

One final note: I’ve been checking the reviews on AMO for Flagfox less often these days, as they seem to have a rather bad spam/abuse problem at the moment. AMO reviews have never been a good contact method for anyone, so please don’t expect replies there, let alone quick. Bug reports and support requests should only be posted in any addon’s reviews as an act of desperation after all other contact channels have been exhausted.


3 thoughts on “Flagfox 6.1.2 and 5.2.10 updates released

    • Sorry, that’s not how things are going. You’re going to have to upgrade at some point, whether you like it or not. Continuing to use a no-longer-maintained, and thus insecure, version of a web browser makes yourself a danger to yourself and others, and it’ll eventually need upgrading to work with newer sites, anyway. I don’t like how Mozilla has dealt with things in the past year, but we’re all hostage to security updates, eventually. 😦

      That said, you’ve still got some time. Flagfox doesn’t complain about the IPDB getting stale for 3 months, and Firefox 52 ESR (probably) won’t be instantly insecure the second it goes EOL.

Comments are closed.