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

Issue 652962 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

MD Settings: Previous scroll position not remembered after using back arrow

Reported by khym.cha...@gmail.com, Oct 5 2016

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36

Steps to reproduce the problem:
1. Go to chrome://md-settings/advanced
2. Scroll down until you see "Site Settings" and click on it.
3. Click on the back arrow within the settings page.

What is the expected behavior?
You'll be back at the old scroll position within chrome://md-settings/advanced

What went wrong?
You'll end up back at the top of the settings page.

Did this work before? N/A 

Chrome version: 53.0.2785.143  Channel: stable
OS Version: Fedora 24
Flash Version: Shockwave Flash 23.0 r0
 
Cc: krajshree@chromium.org
Labels: Needs-Feedback OS-Mac OS-Windows
Unable to reproduce the issue on Ubuntu 14.04, Windows 10 and MAC 10.11.6 using chrome reported version #53.0.2785.143 and latest canary #55.0.2883.0.
Attached a screen cast for your reference.

Following are the steps followed to reproduce the issue.
------------
1. Navigated to chrome://md-settings/advanced
2. Scrolled down to "Site Settings" and clicked on it.
3. Clicked on the back arrow within the settings page.
4. Observed that it came back at the old scroll position within chrome://md-settings/advanced

Reporter@ -  Could you please check this issue on latest canary #55.0.2883.0 by creating a new profile without any apps and extensions and please let us know if the issue persist or not.
652962.mp4
1.4 MB View Download
Well, huh, I'm not able to reproduce anymore with my standard Stable profile/install.
Status: WontFix (was: Unconfirmed)
Based on comment#2 and 1 marking the bug as wontfix.

Sign in to add a comment