-
Notifications
You must be signed in to change notification settings - Fork 323
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
Remove "filesystem" URL scheme #846
Comments
hi @annevk can you please tell me more about this issue, i would like to give this a try. Thank you |
This would require removing the three occurences of "filesystem" in the standard, along with corresponding text for the third instance. (You can ignore "needs tests". I'm not sure how I imagined to test for this. I don't think that's actually possible.) |
thank you , will surely look into it this weekend. Also please go easy on me, i have very rarely collaborated in large public project 🐌 |
I think this could be tested, by creating a fetchable file using the Chrome-only filesystem APIs and then trying to fetch() it. |
As a Chrome-only test? That doesn't seem like a good fit for wpt. |
Well, we could make the test also pass if those Chrome-only APIs weren't present, I guess. Like, we'd have a historical test saying those Chrome-only APIs weren't present, then a second historical test saying "if they are present, filesystem URLs should not work". |
Filed web-platform-tests/wpt#15525 on that idea. |
This is not defined to have an effect. I.e., the ideas in https://www.w3.org/Bugs/Public/show_bug.cgi?id=25734 never materialized. See also #3862 and whatwg/fetch#846.
As far as I know there's only one implementation. Also need to add historical tests.
The text was updated successfully, but these errors were encountered: