Open Bug 1413819 Opened 8 years ago Updated 3 years ago

Removing all handlers of a protocol does not remove the protocol

Categories

(Firefox :: File Handling, defect, P5)

56 Branch
defect

Tracking

()

Tracking Status
firefox57 --- wontfix

People

(Reporter: microrffr, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0 Build ID: 20171024165158 Steps to reproduce: Add a protocol handler with registerProtocolHandler. Here's an example snippet for doing that copied from MDN: https://jsfiddle.net/yv2g05b1/ Go to the browser options, in General, under Files and Applications, scroll down to web+burger, select Burger handler, and click Remove. No handlers remain. Click OK. Actual results: web+burger still remains in list, now set to Always ask. Expected results: should be removed from the list entirely, imo Where are these stored? I want to clean them up manually.
Component: Untriaged → File Handling
These are stored in the "handlers.json" file in the application profile. Removing entries that are reverted to the default from the settings enumeration looks sensible, but is a very low priority.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P5

Please fix this. Because of this open in Github desktop doesn't work. https://github.com/desktop/desktop/issues/5792

Any news about it?

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.