Thanks for the suggestions.
There’s currently no reliable way to identify which browser Kee is executing within. We can make a good guess between Firefox and Chromium (but not all their differently named variants). A good guess is not good enough when presenting this class of information to users so I think we’d need support from the browser manufacturers to make this change in a reliable fashion. If we can’t make it 100% reliable it’s arguably a regression from the current generic “browser addon” information.
I wonder if changing “addon” to “extension” would help? That’s what Chromium browsers call Kee and Mozilla are increasingly switching their user-facing naming from “addon” to “extension” so I think it also makes sense to Firefox users now?
Possibly could check for minimized state on every window before initiating a new SRP connection attempt: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/windows/WindowState
Not sure I want to couple UI state to the backend in this way though. Also would have to check exactly what this “background mode” is in Chrome and how it behaves with respect to the WebExtensions API linked above and whether it will be affected by Manifest v3 changes.
Do many others come across this same confusion with this dialog message?