Consider a different process for standardizing registerProtocolHandler schemes #9158
Description
It's not clear that Chromium, Gecko and WebKit should be gatekeepers for adding schemes to registerProtocolHandler(), since the interest to add a new scheme may be for something that are not relevant for browsers. I received feedback internally at Mozilla that we'd prefer a process where we don't need to be consulted for adding to the list of supported schemes.
Thoughts?