-
Notifications
You must be signed in to change notification settings - Fork 136
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
Keep blob: URLs containing file: origins as an exercise for the reader #780
Conversation
@CanadaHonk I suppose Gecko is supportive? |
See whatwg/url#780 for context.
I agree but I don't represent Gecko, not sure who to ping for this either. |
@valenting or @ricea? |
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.
Seems fine editorially; I haven't tracked down the history motivating this change.
Chromium is supportive (because it moves our implementation closer to compliance). |
See whatwg/url#780 for context.
See whatwg/url#780 for context.
…ned origins, a=testonly Automatic update from web-platform-tests URL: file: URLs have implementation-defined origins See whatwg/url#780 for context. -- wpt-commits: 373be7b4252952bc90d515be07b2dbd9ff60540a wpt-pr: 41158
…ned origins, a=testonly Automatic update from web-platform-tests URL: file: URLs have implementation-defined origins See whatwg/url#780 for context. -- wpt-commits: 373be7b4252952bc90d515be07b2dbd9ff60540a wpt-pr: 41158
See whatwg/url#780 for context.
Blocklisting blob: URLs containing a file: origin from getting a proper origin was a bridge too far. See #506 for a slightly less ambitious approach that could still work.
Closes #775.
(See WHATWG Working Mode: Changes for more details.)
Preview | Diff