Provide an option to disable Navigator.registerProtocolHandler
Categories
(Core :: DOM: Core & HTML, enhancement)
Tracking
()
People
(Reporter: bugsgalore, Unassigned)
References
Details
(Keywords: nightly-community)
Firefox should provide an option to disable the Navigator.registerProtocolHandler feature if a user does not want to allow websites to register themselves as "web applications" for handling protocols.
Updated•4 years ago
|
That bug is about offering a "do not ask again" option in the specific notification.
This bug is about disabling the feature altogether, i.e. have no notification to associate a scheme with a webpage in the first place.
I will never want to associate any webpage with a specific scheme, the feature only causes issues.
When I asked in 668577 this was duped to, "how to disable this feature completely?", the comment was marked off-topic. I.e. it is not relevant to that bug.
So, reopening, as this bug is not a duplicate, but a separate issue as demonstrated by the fact the specific subject of this bug was marked as off-topic/irrelevant in 668577.
Agreed. This bug is present, and relevant, and highly annoying. It's been around for years, and Mozilla keeps ignoring it.
It is now getting worse, as more and more invasive prompts are showing up, with no way to stop it.
Edge, Chrome, and others ALL have a "Do Not Ask Again" option - Why doesn't Firefox???
Updated•4 years ago
|
Comment 4•4 years ago
|
||
Setting this enhancement to NEW in order for it to gain visibility.
Comment 5•4 years ago
|
||
Hey Mozillians,
We recently released the usage Navigator.registerProtocolHandler
on ProtonMail, our users were asking for it. But we face the same limitation as described here. Users that doesn't want to accept it still see the prompt each time and there is no way to tell "Do Not Ask Again".
In our side, we can't tell if the user already have accepted it or not, looks legit for security reasons... Yet it explains that we don't really have more options than just call it everytime and relying on the browser to offer a "Do Not Ask Again" option.
Comment 6•4 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::DOM: Core & HTML' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Comment 7•4 years ago
|
||
Anne, could you consider the priority and severity for this enhancement bug?
Comment 8•4 years ago
|
||
I think we should fix bug 668577. I don't see a reason to offer UI for disabling it completely at this point, but I'll defer to Gijs/Johann.
Comment 9•4 years ago
|
||
(In reply to matthieu.lux from comment #5)
Hey Mozillians,
We recently released the usage
Navigator.registerProtocolHandler
on ProtonMail, our users were asking for it. But we face the same limitation as described here. Users that doesn't want to accept it still see the prompt each time and there is no way to tell "Do Not Ask Again".
You should make the call in response to explicit user action instead of all the time on page load (which, in my testing, doesn't do anything on blink anyway). Your users are definitely not asking you to ask them every time they load any page...
(In reply to Anne (:annevk) from comment #8)
I think we should fix bug 668577. I don't see a reason to offer UI for disabling it completely at this point, but I'll defer to Gijs/Johann.
I defer to Johann but I agree that doing per site and/or per site-protocol permissions would appear to be more useful than removing the capability from all sites.
Comment 10•4 years ago
|
||
I agree with Anne (and Gijs) but I'm not sure we have the resources to do any of this in the short term.
Comment 11•4 years ago
|
||
So I still agree with Anne's initial decision to dupe or close the bug as WONTFIX. I'm not actually sure to which extent this is regulated by about:config prefs and we could talk about to which extent we'd take a patch for additional prefs, but I don't see us adding additional preferences UI for this outside of bug 668577.
Comment 12•4 years ago
|
||
Thanks, closing this as WONTFIX then as OP doesn't consider it a duplicate.
Description
•