Use relevant settings object for pushState/replaceState URL parsing - #1479
Merged
Merged
Conversation
Tested by https://url-parsing-entry-iaqyojravh.now.sh/entry/entry.html; all browsers use relevant, instead of entry, at least for URL parsing. Further testing is needed for the origin checks. Part of #1431.
domenic
force-pushed
the
pushstate-replacestate
branch
from
June 30, 2016 22:42
71e7d44 to
13b8769
Compare
26 of 31 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Tested by https://url-parsing-entry-iaqyojravh.now.sh/entry/entry.html;
all browsers use relevant, instead of entry, at least for URL parsing.
Further testing is needed for the origin checks.
That test also confirms that window.open() uses entry in all browsers, which is sad :(
Part of #1431.