New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 663489 link

Starred by 2 users
Status: Duplicate
Merged: issue 662014
Owner:
creis@chromium.org
Closed: Nov 2016
Cc:
█ kenjibaheux@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Clicking back on a Vox.com article skips back two items

Project Member Reported by komoroske@chromium.org, Nov 8 2016 
Version: 53.0.2785.154 (Official Build) (64-bit)
OS: ChromeOS; also experienced on mobile

What steps will reproduce the problem?
(1) Open a new tab
(2) Navigate to vox.com
(3) Before the page FULLY loads (it will take a very long time to fully complete) Tap a link to one of the articles
(4) Before the article fully loads, hit the back button

What is the expected output?

You go back to vox.com

What do you see instead?

You go back to NTP, skipping over vox.com



This behavior seems very weird. Presumably it would apply to any page that takes a very long time to load all of the non-primary content?

Comment 1 by csharrison@chromium.org, Nov 8 2016

Components: UI>Browser>Navigation
I'm guessing they are improperly using history.replaceState for their articles. This should not happen in general. The navigation entry in the history list will be set after the load commits.

If you e.g. go to vox.com and then in the omnibox navigate to http://www.vox.com/policy-and-politics/2016/11/8/13421576/watch-election-results

the back button works properly.

Comment 2 by komoroske@chromium.org, Nov 9 2016

Status: WontFix (was: Untriaged)
Ah, makes sense. That would also explain why I don't see it on other sites (that I've noticed).

So the problem is that they're using replaceState when they should just be using pushState?

Comment 3 by csharrison@chromium.org, Nov 9 2016

Status: Untriaged (was: WontFix)
I just tested this on FF and it does not repro, so let's move it back to untriaged.

I'm not sure what they are doing, I was merely guessing about the replaceState. Tossing this into navigation those folks to take a look.

Comment 4 by droger@chromium.org, Nov 18 2016 

I could repro on Chrome linux, but not on Firefox linux.
Seems navigation related indeed.

Comment 5 by creis@chromium.org, Nov 18 2016

Cc: kenjibaheux@chromium.org
Mergedinto: 662014
Owner: creis@chromium.org
Status: Duplicate (was: Untriaged)
Looks like this is a dupe of issue 662014, which I haven't had a chance to investigate.  Goes way back to at least Chrome 21 and probably much earlier.
►

Sign in to add a comment