Safelist 'notes' scheme
Categories
(Core :: DOM: Core & HTML, enhancement)
Tracking
()
People
(Reporter: dconmy, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.83 Safari/537.36
Steps to reproduce:
Trying to register a handle for the notes protocol.
Actual results:
A "SecurityError" DOMException is thrown as the scheme is not safelisted.
Expected results:
This is expected. I am filing this as the notes URI scheme is in use, and a whatwg has been opened to safelist. https://datatracker.ietf.org/doc/draft-dconmy-notes-uri-scheme/
Whatwg upstream issue: https://github.com/whatwg/html/pull/7678
An issue has been opened with Chromium, https://bugs.chromium.org/p/chromium/issues/detail?id=1300279, and they "interested in implementing , as long as the feedback in your HTML pull request is addressed."
|
||
Comment 1•4 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Performance' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
May I get confirmation that maintainers are interested, or that this would be implemented after the scheme is accepted by whatwg?
A statement similar to the comment on chromium's bugtracker would be fine.
|
||
Comment 3•3 years ago
|
||
I think if Anne is fine with it this should be trivial to implement. He seems to have already provided feedback on the HTML spec issue.
(In reply to Emilio Cobos Álvarez (:emilio) from comment #3)
I think if Anne is fine with it this should be trivial to implement. He seems to have already provided feedback on the HTML spec issue.
How can I move this forward?
|
|
||
Comment 5•3 years ago
|
||
Writing a patch for this should be trivial, so if you want to send it that'd be great. But what really needs to move forward is the spec PR.
(In reply to Emilio Cobos Álvarez (:emilio) from comment #5)
Writing a patch for this should be trivial, so if you want to send it that'd be great. But what really needs to move forward is the spec PR.
As I understand it, can you state that mozilla is interested in implementation which will move the spec PR forward?
Chrome has indicated interest, and I need either mozilla or safari to express implementation interest to move the spec PR forward.
Description
•