Flagfox 6.1 Beta 3

The third and final Flagfox 6.1 beta is ready for testing. You can now download and install from the downloads page here (it will not auto-update from the first beta, but will auto-update to the final release).

Flagfox 6.1b3 changelog:

  • Added support for importing actions into options from prefs/actions JSON files
  • Replaced now-defunct URL Parser default action with simple built-in JS action
  • Fixed error message spew from hotkey migration on startup (regression in 6.1 beta)
  • Various code cleanups/fixes

Flagfox 6.1b2 changelog:

  • Added local caching for all favicons (uses localStorage; clears with cache clear)
  • Added throttling to favicon fetching while editing an action’s template
  • Reimplemented default icon loading for missing favicons in menus
  • Fixed handling of raw IPs (e.g. router admin pages; regression in 6.1 beta)

Flagfox 6.1b1 changelog:

  • Reimplemented support for fetching IPs from the DNS cache, instead of only requests (new WebExt API)
  • Reimplemented support for customizable hotkeys for actions, instead of just one default (new WebExt API)
  • Reimplemented action availability check on menu open, instead of all tab changes (new WebExt API)
  • Improved startup to attempt to load icons into existing tabs, where possible
  • Rewrote IP/host cache, yet again (having the DNS API makes things way less complex now)
  • Added support for all action types in context menus, where now possible (IPs obtainable via DNS cache)
  • Changed hotkey pref save format to match new API; old ones from Flagfox 5.2.x will be imported
  • Added detection and indication of invalid or existing hotkeys, when setting (not 100%, due to iffy API)
  • Added ability to undo a hotkey change without having to cancel config, via escape key
  • Switched to PointerEvents where applicable (only minor use)
  • Improved opening of new tabs to use openerTabId; now opened next to subject, instead of end of strip
  • Support for Tree Style Tabs addon (and similar) is now available again due to openerTabId change
  • Dropped now-defunct XMarks action from defaults
  • Various code cleanups
  • Dropped support for Firefox 56-59, as Mozilla only finally added the new APIs used here in Firefox 60

The new import from JSON file works just like the old import works, by dragging/dropping the file (e.g. from desktop/wherever) onto the actions list in the Flagfox options. The format can be any of the 3 supported by Flagfox: the format the default actions JSON file is in, the format the user actions preference is in, or the format the WebExt preferences storage file is in. Note that if it’s not the full format (the first in that list), old default actions can’t be imported, because they’re not actually saved in the user pref (which saves a lot of space). Yes, this means you can take any Flagfox 5.2+ storage.js file from your Firefox profile and dump it into Flagfox 6.1+, and it’ll figure it out and import it as a pile of new custom actions. (you can, of course, delete any you didn’t want, afterwards) The old text list format is still supported, and can still be from a file or a copied/pasted/dragged text selection.

Important: There are a couple dozen people in this beta test now, but not one of you has actually provided any feedback. If nobody actually tests the custom hotkey support on a Mac, then I’m going to have to release it in its current “¯\_(ツ)_/¯” state. Thus far, the only use I’ve gotten from this beta is me learning how to sign XPIs for off-AMO hosting so I can test in my main profile. Even with Mozilla killing off the AMO beta channel, this getting so much less testing than all past betas is a bit disappointing. :/

Known Issues:

  • Keyboard shortcuts are limited to one of Ctrl/Alt (or Command, on Mac), potentially Shift, with a character key. (WebExt API restriction)
  • Keyboard shortcuts have not yet been tested on a Mac.
  • There is a limit of 100 keyboard shortcuts allowed at one time.

(See first post for more detail on the keyboard shortcut known issues.)

As this is a beta test, bugs are always a possibility and should be reported in a comment below or via any other contact method. Please don’t assume an issue is known unless I state so in a blog post somewhere here. I’ll update this blog post with any significant known issues discovered before posting the next version. Also, please only use the latest beta version, which unfortunately must be done manually due to Mozilla killing the beta channel.