-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Pass a request, rather than URL, to Navigate algorithm #3642
Conversation
@annevk, can you take a look? |
source
Outdated
substeps:</p> | ||
|
||
<ol> | ||
|
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.
Please remove this newline.
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.
Done.
source
Outdated
this case, the navigation will result in a different page than previously; for example, it | ||
might be an error message explaining the problem or offering to resubmit the form.</p> | ||
</li> | ||
|
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.
As well as this.
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.
Done.
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.
This seems fine, but what's the upside of doing this? Are you planning a subsequent change that does something else here?
I'll set request's history-navigation flag for w3c/ServiceWorker#1167 in a subsequent change. You once talked about setting request's method depending on the history entry, this change would also be beneficial for that change. |
I addressed some nits, but upon further reading it seems this introduces a regression as you no longer return. I'll fix that, but someone else will need to review again to make sure we haven't missed anything. |
Thanks! |
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.
LGTM with nit
source
Outdated
<li> | ||
<p><span>Navigate</span><!--DONAV history traversal after eviction--> the <span>browsing | ||
context</span> to <var>request</var> to perform an <span>entry update</span> of | ||
<var>entry</var> and return. The navigation must be done using the same <span>source browsing |
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.
"And return" was really easy to miss here since there's a sentence and two notes after it. I'd suggest making it step 1.3.
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.
Done.
This is a preliminary refactoring for history-navigation request attribute introduction. With this change,
Traverse the history algorithm passes a request, rather than a URL, to Navigate algorithm. This change
doesn't change the behavior.
/browsing-the-web.html ( diff )