Only use sourceOrigin for all about:-schemed Documents #9465
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before this PR, determine the origin took in two origins: sourceOrigin (returned for
about:blank
URLs) and containerOrigin (returned forabout:srcdoc
). But I don't think there's a reason for these two be different, so this CL combines them.When navigating a srcdoc iframe via the srcdoc attribute, the parent is always used as the sourceDocument passed into the #navigate algorithm, which means that the container origin used here and here for srcdoc iframe navigations, is the initiator/source origin. That, coupled with the fact that there's no instance where we pass in sourceOrigin and containerOrigin together (for the algorithm to decide between), means they are exclusive, but both used for about:-schemed documents, and generally feel redundant IMO.
/browsing-the-web.html ( diff )
/document-sequences.html ( diff )