Closed Bug 1871955 Opened 1 year ago Closed 1 year ago

Add "lbry" to the registerProtocolHandler allowlist

Categories

(Core :: DOM: Core & HTML, enhancement)

Firefox 121
enhancement

Tracking

()

RESOLVED WONTFIX

People

(Reporter: ben221199, Unassigned)

References

(Blocks 1 open bug)

Details

Steps to reproduce:

I opened the console and entered the following line:

navigator.registerProtocolHandler('lbry','https://example.com/lbry/%s');

Actual results:

The console returned the following error:

Uncaught DOMException: Navigator.registerProtocolHandler: Permission denied to add a protocol handler for lbry

Expected results:

The function should return undefined and the browser should ask if I wanted to add this protocol handler.

The list of allowed schemes does not include lbry. You can ask the HTML spec to be extended.

Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Resolution: --- → INVALID

I have created an issue and a pull request on the HTML repository of WHATWG: https://github.com/whatwg/html/issues/9016 and https://github.com/whatwg/html/pull/9017. Before WHATWG wants to add lbry to the allowlist, I need 2 implementers being interested and also have bugs filed, so that is what I did.

You should have definitely written that in your initial message.

Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: INVALID → ---
Blocks: 1056860
Component: Untriaged → DOM: Core & HTML
Product: Firefox → Core
Summary: Add "lbry" to the protocol handler allowlist → Add "lbry" to the registerProtocolHandler allowlist

Can I conclude that Mozilla is interested in implementing this as soon as the spec is updated? In that case I will add a comment on the issue. Chromium already agreed.

Hi @peterv, can I conclude that Mozilla is interested in implementing this as soon as the spec is updated? In that case I will add a comment on the issue. Chromium already agreed. WebKit cannot implement it yet, because they don't support registerProtocolHandler at this moment.

Flags: needinfo?(peterv)

Well, there's also https://github.com/whatwg/html/issues/9158 which we might want to do instead.

(In reply to Ben [:ben221199] from comment #5)

Hi @peterv, can I conclude that Mozilla is interested in implementing this as soon as the spec is updated?

And no, you shouldn't conclude that. The github issue is where we would note our interest.

We'd like to change this process, as :peterv noted above, so that we have less of a gatekeeping role here. In the meantime we don't have any particular interest in this scheme.

Status: REOPENED → RESOLVED
Closed: 1 year ago1 year ago
Flags: needinfo?(peterv)
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.