Implement usage of custom protocol handlers#40803
Conversation
a3cec27 to
defdd0c
Compare
defdd0c to
08a2bca
Compare
|
08a2bca to
18efe04
Compare
18efe04 to
5610402
Compare
|
🔨 Triggering try run (#19595453061) for Linux (WPT) |
|
Test results for linux-wpt from try job (#19595453061): Flaky unexpected result (41)
Stable unexpected results that are known to be intermittent (25)
|
|
✨ Try run (#19595453061) succeeded. |
5610402 to
4e1270a
Compare
mrobinson
left a comment
There was a problem hiding this comment.
I'll let folks more familiar with the fetch implementation review the meet of this, but I have a comment about the servoshell chage:
|
This seems useful for something like a Presumably this would be implemented by returning some kind of "cancel navigation" (where this is differentiated from an error state, but the result is that Servo does nothing), with the action actually triggered by the custom handler as a side effect. |
|
|
|
This is indeed the standard API that dictates how to navigate these URLs. If an embedder wants do implement custom logic for a particular scheme, they can already do so with the existing |
4e1270a to
dc1c964
Compare
|
Added @jdm as reviewer for the Fetch parts |
dc1c964 to
d7fd5c0
Compare
mrobinson
left a comment
There was a problem hiding this comment.
Looks good from my perspective. Thanks for reverting the servoshell bits.
d7fd5c0 to
2b73712
Compare
|
Rebased and also replaced the |
2b73712 to
f84ed36
Compare
This implements a dummy `mailto:` protocol handler in Servoshell. It registers a new custom handler that fetches content by substituting the registered url for the protocol handler. This does not pass any WPT tests, as that requires using the `document.protocol_handler_automation_mode` which will be part of a follow-up PR. Part of servo#40615 Signed-off-by: Tim van der Lippe <[email protected]>
f84ed36 to
dafb772
Compare
This implements a dummy
mailto:protocol handler inServoshell. It registers a new custom handler that
fetches content by substituting the registered url
for the protocol handler.
This does not pass any WPT tests, as that requires
using the
document.protocol_handler_automation_modewhich will be part of a follow-up PR.
Part of #40615