-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add FTP related protocols to the registerProtocolHandler
safelist.
#6584
Conversation
Adding @domenic as well. I updated the PR description to reflect that Firefox has reacted positively to the proposed change. |
In the discussion with @valenting you mentioned removing credentials. Is that something you ended up pursuing? If so, it should probably be part of the standard, no? (Although I suppose we can only really do it for |
Yes, per the change in https://chromium-review.googlesource.com/c/chromium/src/+/2826871 it looks like that is what was implemented. @asankah can you update this PR to specify that behavior? |
@asankah ping on updating the PR to match what Chromium does. |
@domenic @annevk I looked at adding it, but the spec already contains the following text:
This already captures what was agreed upon regarding how |
@asankah the ask is to make that explicit in the processing model. And perhaps it should be exclusively in the processing model, as it's not clear if that note also applies to |
@annevk Ohh. Gotcha. I'll update the patch to address that. |
Hey @asankah, is this still on your radar? We've been thinking of shipping this behavior in Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1705202. cc @valenting |
@asankah @annevk Any more news on this? I'm hoping to update the MDN documentation, but if https://bugzilla.mozilla.org/show_bug.cgi?id=1705202 goes in and this PR does not then I will need to update browser compatibility data in a more complicated way, as this will end up being non-spec behavior in a released platform |
Whoops. Yeah, on it. |
The rebase appears to have gone poorly, could you retry? |
223c6bb
to
18694ba
Compare
@@ -98495,14 +98512,6 @@ interface <dfn interface>Navigator</dfn> { | |||
allowing administrators to disable custom handlers on certain subdomains, content types, or | |||
schemes.</p> | |||
|
|||
<p><strong>Leaking credentials.</strong> User agents must never send username or password |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that I removed the Leaking Credentials section since it is addressed in the processing steps.
The part about resources that may require credentials is, I believe, addressed in the "Leaking private data" section which warns about private URLs in general.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Will give it a day in case @annevk wants to do an additional review.
`registerProtocolHandler` allows registering `ftp`, `ftps`, and `sftp` protocols as of whatwg/html#6584. This change adds tests to ensure that `registerProtocolHandler` allows registering those protocols and to ensure that embedded credentials are removed prior to invoking the custom protocol handler.
`registerProtocolHandler` allows registering `ftp`, `ftps`, and `sftp` protocols as of whatwg/html#6584. This change adds tests to ensure that `registerProtocolHandler` allows registering those protocols and to ensure that embedded credentials are removed prior to invoking the custom protocol handler.
`registerProtocolHandler` allows registering `ftp`, `ftps`, and `sftp` protocols as of whatwg/html#6584. This change adds tests to ensure that `registerProtocolHandler` allows registering those protocols and to ensure that embedded credentials are removed prior to invoking the custom protocol handler.
`registerProtocolHandler` allows registering `ftp`, `ftps`, and `sftp` protocols as of whatwg/html#6584. This change adds tests to ensure that `registerProtocolHandler` allows registering those protocols and to ensure that embedded credentials are removed prior to invoking the custom protocol handler.
`registerProtocolHandler` allows registering `ftp`, `ftps`, and `sftp` protocols as of whatwg/html#6584. This change adds tests to ensure that `registerProtocolHandler` allows registering those protocols and to ensure that embedded credentials are removed prior to invoking the custom protocol handler.
`registerProtocolHandler` allows registering `ftp`, `ftps`, and `sftp` protocols as of whatwg/html#6584. This change adds tests to ensure that `registerProtocolHandler` allows registering those protocols and to ensure that embedded credentials are removed prior to invoking the custom protocol handler.
Closes #6583
registerProtocolHandler
.registerProtocolHandler
)(See WHATWG Working Mode: Changes for more details.)
/system-state.html ( diff )
/acknowledgements.html ( diff )
/system-state.html ( diff )