State: Selecting a profile should automatically toggle on the header's switch

[redactedscribe]

Firstly, thank you for your extension. But upon my first few minutes of using it, I encountered an issue, and the more I've used it, the more confusing the operation of choosing profiles and toggling the header switch has become (there are also profile switching bugs which have already been reported).

Here are the steps to reproduce the initial issue:

1. Header switch is toggled enabled / on.
2. "Always On" profile is selected (green tick / checkmark).
3. Click a disabled extension to enable it (e.g. named "X"): "Always On" loses green tick.
4. Toggle header switch off: Extension X gets disabled.
5. Enable "Always On" profile: Gets green tick again.
6. Toggle header switch on: Extension X gets enabled + "Always On" profile still has green tick.

This UI state is misleading, because like in step 3, it's expected for a profile to no longer be ticked when an extension outside of the profile is enabled or disabled. There are other variations to this misleading state, like disabling an enabled extension (instead of enabling a disabled extension as the above example illustrates, i.e. step 3).

A misleading UI state is one issue, but correcting that is not enough because the issue is actually a UX one. Fixing the UX will also fix the inconsistency of the green tick state:

Please make the operation of selecting profiles and toggling states more predictable and less confusing. It can be done by ensuring that in the particular case where a user enables a profile when the header switch is toggled off, toggling the switch back on should do nothing as it should be considered that the user chose to override the what-was-enabled state by choosing a profile. In fact, the header switch should toggle back on automatically in this case.

After more thinking, it's unfortunate that I have to say this but the profile selecting and header switch toggling is just poorly designed; it's unnecessarily confusing to use (at minimum, unintuitive). This may be due to the extension's old age and ideas having changed over time...and so I've created a proposal for how the extension could be redesigned.

Thanks.