Open
Conversation
Contributor
|
Preview URLs (2 pages) |
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
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.
Fixes #41483, fixes #41482.
At least that's the idea.
My understanding of this, mostly from testing, is that Client.url isn't updated unless an actual page load happens, which means it isn't updated in situations such as:
<a href="#thing>go to thing</a>This is unituitive, partly because the value of
Client.urlwould in these cases not matchdocument.location.hrefor the URL bar.I've tested this, and have tried to express it. I'm not sure what the best language to use here is though.
Side note, the Navigation API docs are lacking any guide docs. I had to read https://developer.chrome.com/docs/web-platform/navigation-api to understand how to use it, and that guide although good is quite out of date.