Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upEnsure that a navigation to the same URL is aborted. Fixes #10952. #10954
Conversation
highfive
commented
May 1, 2016
|
Heads up! This PR modifies the following files:
|
|
-S-awaiting-review +S-needs-code-changes r=me after that small nit. Reviewed 4 of 4 files at r1. components/script/script_thread.rs, line 1791 [r1] (raw file): Comments from Reviewable |
|
Review status: all files reviewed at latest revision, 2 unresolved discussions. components/script/script_thread.rs, line 1800 [r1] (raw file): Comments from Reviewable |
|
Review status: all files reviewed at latest revision, 2 unresolved discussions. components/script/script_thread.rs, line 1800 [r1] (raw file): This seems to be the expected behaviour given the spec section for
So not sure if the "navigate" algorithm spec should be updated to take into account null fragments, or if there's another bug in our code that should make us arrive with an url fragment (which doesn't seem to be the case, but I haven't looked too deeply at it). Comments from Reviewable |
|
I've filed whatwg/html#1177 about this. |
|
|
|
I think this should probably be rebased and landed while we wait for input in whatwg/html, there are quite a few pages affected. What do you think @jdm? I can do the rebase if you're busy btw :) |
|
I am inclined to agree, with a comment that links to the whatwg issue. If you could do the rebase, that would be swell! |
|
Rebased in #11321 |
jdm commentedMay 1, 2016
•
edited by larsbergstrom
This change is