Split the definition of web-based protocol handler from the definition of registerProtocolHandler

[SoniEx2]

Recent PWA support for protocol handlers would benefit from splitting it off of registerProtocolHandler. A web-based protocol handler should just be an endpoint that follows the protocol handler template - but it need not be passed to registerProtocolHandler to be considered a web-based protocol handler.

[annevk]

I thought that specification already integrated with this one?

[SoniEx2]

It would genuinely clarify things so much to separate a "web-based protocol handler" from "a call to registerProtocolHandler".

[annevk]

Can you point me to the definition that is confusing? I agree that they shouldn't directly invoke this method, that is unlikely to work.

[SoniEx2]

Sure. The title of this section: https://html.spec.whatwg.org/multipage/system-state.html#custom-handlers is: "Custom scheme handlers: the registerProtocolHandler() method", which directly references registerProtocolHandler() and is pretty much entirely defined by registerProtocolHandler().

[annevk]

I'm familiar with that section, I was asking about the other specification trying to reuse it.

[SoniEx2]

Well we also wanna reference web-based protocol handlers in our talks without having to spend 10 minutes separating them from registerProtocolHandler...

[annevk]

A talk is not sufficient motivation to change a standard.

[SoniEx2]

It is if it highlights clarity issues with the standard.

Like, this isn't even a functional change, it's merely an editorial one.