New issue
Advanced search Search tips

Issue 690844 link

Starred by 2 users

Issue metadata

Status: Unconfirmed
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

canGoForward() API is bhaving differently for some navigation

Project Member Reported by ajit...@samsung.com, Feb 10 2017

Issue description

Chrome Version: 54.0.2840.100 
OS: Android, Linux

What steps will reproduce the problem?
(1) Load m.entertain.naver.com
(2) After page load finished, select an article.
(3) After page load is finished, start typing amazon.com in URL bar
(4) After page load finished, press back key or back button from the window
(5) Observe Forward button state is toggling for few duration (It's state is toggling between enable and disable during the transition)

What is the expected result?
There should be only one state change, Continuous toggling should not happen

What happens instead?
Continuous toggling is happening, hence it's observing as flickering.

Additional Info: canGoForward() API is returning true for sometimes, and false for sometimes until state is gets stable at true state.
Navigation entry count and last committed entry index is coming same during the issue scenario. Issue is observed only in this scenario, other scenario, it works well.
 
Components: UI>Browser>Mobile UI>Browser>Navigation
clamy@/alexmos@ - is there someone familiar with Chrome's navigation stack that can pick up this bug?

UI>Browser doesn't seem like the quite the right set of owners.

Comment 3 by clamy@chromium.org, May 16 2018

This bug seems to predate the launch of PlzNavigate (aka navigation refactoring). Do we know if it's still happening post-PlzNavigate?
Labels: Needs-Feedback Needs-TestConfirmation
Status: Unconfirmed (was: Untriaged)

Sign in to add a comment