Skip to content
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 WPT for blocked navigation to about:srcdoc #28540

Merged
merged 1 commit into from May 6, 2021

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Apr 16, 2021

Navigations to "about:srcdoc" should fail per the HTML specification.
Indeed, as per [1] the "about:srcdoc" URL is "unresovable". This URL
is never handled (i.e. treated with an appropriate locally-created
response) anywhere in the navigation algorithm [2]. In fact the only
time it ever seems to be handled is in the process the iframe
attributes algorithm [3], which is not invoked when navigating via
window.open() or via setting window.location.

This CL adds tests for this.

[1] https://html.spec.whatwg.org/multipage/urls-and-fetching.html#about%3Asrcdoc
[2] https://html.spec.whatwg.org/#navigating-across-documents
[3] https://html.spec.whatwg.org/multipage/iframe-embed-object.html#process-the-iframe-attributes

Bug: 1169736
Change-Id: I6e92b6c930a15fc77aff3ee700a6b01b107e1d41
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2831536
Commit-Queue: Antonio Sartori <antoniosartori@chromium.org>
Reviewed-by: Dominic Farolino <dom@chromium.org>
Reviewed-by: Domenic Denicola <domenic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#879713}

Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The review process for this patch is being conducted in the Chromium project.

Navigations to "about:srcdoc" should fail per the HTML specification.
Indeed, as per [1] the "about:srcdoc" URL is "unresovable". This URL
is never handled (i.e. treated with an appropriate locally-created
response) anywhere in the navigation algorithm [2]. In fact the only
time it ever seems to be handled is in the process the iframe
attributes algorithm [3], which is not invoked when navigating via
`window.open()` or via setting `window.location`.

This CL adds tests for this.

[1] https://html.spec.whatwg.org/multipage/urls-and-fetching.html#about%3Asrcdoc
[2] https://html.spec.whatwg.org/#navigating-across-documents
[3] https://html.spec.whatwg.org/multipage/iframe-embed-object.html#process-the-iframe-attributes

Bug: 1169736
Change-Id: I6e92b6c930a15fc77aff3ee700a6b01b107e1d41
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2831536
Commit-Queue: Antonio Sartori <antoniosartori@chromium.org>
Reviewed-by: Dominic Farolino <dom@chromium.org>
Reviewed-by: Domenic Denicola <domenic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#879713}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants