Extension redesign ideas for better UX

[redactedscribe]

Due to having noticed some bugs, UI and UX issues after installing this extension, I'd like to propose how it could be redesigned. A more straight-forward design, whilst keeping the ability to toggle between two states, could be as follows:

• The header toggle button should operate like an A-B button found on audio plug-ins. This means the user can set two states, A and B, and switch between them at will (useful for testing one set of extensions vs another).
  • A and B would be considered internal profiles that get defined dynamically: When on A, whichever extensions get enabled or disabled by the user is what sets A. And when on B the same for B.
  • Usually there is a copy button to copy state A to B "[A][>][B]".
  • State of A should persist across browser sessions and be loaded on browser start.
  • State of B is temporary and doesn't persist across sessions.
• Whenever selecting a profile, the state of enabled extensions should be set to that of the profile's, and have A automatically inherit the same state (if B is currently selected, automatically switch to A). Basically, profiles would just be a way to set A's state (use the Copy button to set B after setting A to a profile).
• Checkboxes next to profiles so that multiple can be toggled on at once in an additive manner ([Feature Request] Multiselect Profiles #92). Clicking the profile names would select only that profile (current behaviour).
  • An option to hide the checkboxes and have clicking on profiles always toggle them (i.e. make clicking profiles additive by default).
• New buttons: All Off, All On, Reset, Save.
  • The Reset button would reset the state of enabled and disabled extensions to be the extensions marked as the "Always On" ones.
  • The All Off button would turn off all currently enabled extensions, except the always on extensions (if the user has enabled the "All Off button keeps Always On extensions enabled" option).
    • Two consecutive clicks of the All Off button would ask whether the user wants to force all extensions to disable (including the default ones). If no extensions marked as default, don't display the force all off prompt on second clicking.
  • The All On button would just enable all extensions. To only enable a subset of extensions, select a profile instead.
  • The Save button would save the state of A or B (depending which is selected) over an existing profile or create a new one.

Being new to this extension, I may have missed some key ways of working with it that I'm unaware of, but if you (or someone else) ever decide to re-write it, I hope this serves as some guidance or inspiration.

Thanks.