Went to another site and made a video actually. I can confirm via Notepad it did save, and it is honored as seen in the video. So “magnet” schemas are working, they are saved (just can’t use VS Code to see it for some reason), and remembered. For magnet, it is checking as once “remembered”, it never asks on that domain again.
(After video capturing I did try other magnet links from the same site as you asked, and no, it doesn’t re-prompt, it properly remembered the entire domain).
However, mailto: schemas are not being checked it seems. (Nor anything still visible under Handlers).
(I am slightly worried as to why Preferences won’t format in VS Code, or apparently “load” all the way to find all of the document since VS Code found 1 instance of “magnet” but Notepad found a few more. My preferences file is 456KB in size. Just to test, Local State does properly open up in VS Code, and can be formatted, so VS Code doesn’t seem to be broken, but maybe Preferences is.)
@MasterLink this is what I was correcting myself on earlier. The brave://settings/handlers page will only show default handlers if the associated handler is a website – not if it’s associated with an external application (since these handlers fall under the category of “site permissions”).
I opened issue 52140 above suggesting that we provide a way for users to view what external apps are associated as handlers for links in the browser since there is no way to do it at this time.
Just to confirm, when you test the mailto link opening in an external mail client and check the box, this data is not remembered?
Correct, and it doesn’t seem site specific. So right now, it seems specific to the mailto: schema, but not others. It is in the Preference file that mailto: is set to “true” on the sites I did check “Remember”, but Brave itself appears to not be actually remembering.
Ahh gotcha. Sorry I mis-read the correction.
EDIT: I’m going to test this in Chromium real quick since I never tested mailto: specifically there (only magnet: and well, that’s working on Brave so I need to re-test).
As my test since it has a mailto: URI (this is the same page I used previously on Brave when clicking “Remember” did nothing), I found Chromium doesn’t ask, upon clicking it, Outlook simply opened up. Remember, Chromium’s preference file has nothing in it, it’s new. So Chromium’s behavior is very different to Brave now, since Brave is pushing that prompt like it would with magnet: schemas, but Chromium is not doing this for mailto: schemas, it’s just opening Outlook.
As a secondary test to ensure that Chromium itself didn’t just suddenly not have that prompt, I tried a torrent, and the popup appeared if it should launch Transmission Qt. And when I clicked Remember, it was in Chromium’s preference.
I think this is why on Brave it’s mailto: specific, I think Chromium’s behavior changed as it doesn’t even ask at all now.
To TL;DR this as it’s getting confusing even for me to type (and on a support.brave. app page with a mailto: URI):
Chromium: Never asks on mailto:, simply opens Outlook. Does not have "protocol_handler":{"allowed_origin_protocol_pairs":{"https://support.brave.app":{"mailto":true} in Preferences.
Brave: Always asks to open Outlook, and does have "protocol_handler":{"allowed_origin_protocol_pairs":{"https://support.brave.app":{"mailto":true} in Preferences.
Btw @Mattches, it was VS Code. I noticed it claimed Preferences had 1000 problems, and that was not possible, so I checked the bottom right. It thought it was JavaScript. Changed it to JSON, and now it’s readable and formatted. Thanks Microsoft, that’s the first time I had VS Code get a language wrong before.
I am totally unable to open mailto links using Thunderbird (or any other locally installed mail program).
Also, someone mentioned torrents above, come to think of it I probably have the same issue there as in the past I have asked it to open my torremnt client and it never does, and never remembers!
Thanks Microsoft, that’s the first time I had VS Code get a language wrong before.