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

Issue 711153 link

Starred by 4 users
Status: WontFix
Owner: ----
Closed: Dec 10
Cc:
nyerramilli@chromium.org
dbeam@chromium.org
█ msrchandra@chromium.org
dpa...@chromium.org
jmukthavaram@chromium.org
█ ranjitkan@chromium.org
swarnasree.mukkala@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug



Sign in to add a comment

MD Settings: Exiting content settings subpage always reset scroll position to the top.

Reported by rp...@etouch.net, Apr 13 2017 
Version: 59.0.3070.0 daf91016aa4560f3c0f72d50eee762eed996fc0e-refs/heads/master@{#464226}
OS: Windows (7,8,8.1,10)

What steps will reproduce the problem?
1. Freshly launch chrome, navigate to chrome://md-settings/content
2. Now scroll down the page and click on 'USB devices' or any options and then click on back navigation arrow,observe

Actual: Weird behavior of page is seen after clicking on back navigation arrow  
Expected: Weird behavior of page should not be seen after clicking on back navigation arrow  

This is regression issue, broken in ‘M 59’ and will soon update other info :
Good build:59.0.3069.0
Bad build: 59.0.3070.0
Actual_video.mp4
478 KB View Download
Expected_video.mp4
236 KB View Download

Comment 1 by jmukthavaram@chromium.org, Apr 13 2017

Cc: jmukthavaram@chromium.org
Labels: -Pri-2 hasbisect-per-revision ReleaseBlock-Stable Pri-1
Owner: dpa...@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce this issue on windows 7 with Chrome Canary version-59.0.3070.0 as per steps in Comment#0.

Manual Bisect:
Good build:59.0.3069.0-Revision-463921
Bad build: 59.0.3070.0-Revision-464226

Per revision Bisect Tool Info:
Change Log:
You are probably looking for a change made after 464084 (known good), but no later than 464085 (first known bad).
CHANGELOG URL:
The script might not always return single CL as suspectas some perf builds might get missing due to failure.
https://chromium.googlesource.com/chromium/src/+log/8588407dac066cab5eac58b342b9ebd4f75bc848..f6d9d3d52ed411f5c39948cbb48969f1ccf41192

dpapad@ Kindly take a look and please help us to reassign this issue to a right owner if not with respect to this change.

Thanks.!

Comment 2 by jmukthavaram@chromium.org, Apr 13 2017

Labels: -ReleaseBlock-Stable

Comment 3 by jmukthavaram@chromium.org, Apr 13 2017

Labels: Proj-MaterialDesign-WebUI

Comment 4 by dpa...@chromium.org, Apr 13 2017

Cc: dbeam@chromium.org
Labels: -Pri-1 OS-Linux Pri-2
The previous behavior is buggy already. Exiting a subpage should not reset the scroll position. The only difference now is that because we focus() the anchor element the pages is briefly scrolled at the correct position, before it jumps back to the top.

So not really a regression, just a pre-existing issue. @dbeam and I already talked about this today.

Comment 5 by dpa...@chromium.org, Apr 13 2017

Summary: MD Settings: Exiting content settings subpage always reset scroll position to the top. (was: Regression : Weird behavior of page is seen after clicking on back navigation arrow in chrome://md-settings/content.)
Rephrasing bug title to better reflect the problem.

Comment 6 by dpa...@chromium.org, Apr 13 2017

Labels: -Type-Bug-Regression Type-Bug

Comment 7 by rp...@etouch.net, Apr 13 2017

Labels: OS-Mac

Comment 8 by dbeam@chromium.org, Apr 17 2017

Labels: Hotlist-MD-Settings-Navigation
it would be preferable to just set the focus navigation start point ("focus caret") instead of actually change focus here.

changing focus always scrolls stuff into the visible frame (which is generally a Good Thing), but kind of works against us here.

Comment 9 by tbuck...@chromium.org, Jun 12 2017 

 Issue 731013  has been merged into this issue.

Comment 10 by tbuck...@chromium.org, Jun 12 2017

Labels: -Pri-2 -M-59 M-61 Pri-1
Marking as P1 post-launch

Comment 11 by dpa...@chromium.org, Oct 24 2017

Owner: ----
Status: Available (was: Assigned)
Marking bugs (mostly lower priority ones) that I am unlikely to get to soon as Available.

Comment 12 by dpa...@chromium.org, Oct 4

Cc: swarnasree.mukkala@chromium.org dpa...@chromium.org
 Issue 880250  has been merged into this issue.

Comment 13 by dpa...@chromium.org, Dec 10

Status: WontFix (was: Available)
This is no longer happening after r615011.
►

Sign in to add a comment