For a long time I have noticed a problem with mine and other extensions too. On a new install, an “onboarding page” might unwanted close when you select if an extension is to be allowed to run in Private Windows or not. I don’t know about others, but I instinctively always make my choice in the little “popup” to get rid of that, before I look at content on onboarding page:
But in the moment I make my choice in the popup, the onboarding page has disappeared:
It doesn’t happen for every extension, and I think it depends on if onboarding page is an “internal extension page” or it a standard “external web page”. So a work-around could probably be to make my onboarding page an external webpage. I did however deliberately choose it to be an internal extension-page for privacy reasons, and I would probably also need to change privacy policies for my extensions if I make the switch. So I’m not very keen on doing that.
I’ve been annoyed by but living with the issue so far. Also because it doesn’t happen so often I install an extension (so I’m not reminded of it), and I’m always in doubt if it is still a problem or if it has been fixed when I remember about it. But now I saw the issue again a few days ago when adding one of my extensions to a new Firefox Beta (Developer Edition) installation (the above screenshots).
Anyone know a way to avoid this without using an external webpage?
With the introduction of MV3 and the way host-permissions are going to work, I feel it can become critical that new users get the onboarding experience. When “No, I didn’t just install Flickr Fixr because I think it looks cool in my list of installed extensions, I actually really want to run it”(*) kind of confirmations becomes necessary, I think it needs some kind of help and explanation.
(*) Yes, sorry. I’m being slightly sarcastic here. But I really don’t get the reasoning for the way its planned to handle host-permissions.
And I’m the only one concerned about this bug? Maybe even the only one experiencing it?