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

Issue 774153 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Unexpected and unwanted scroll behaviour on focus()

Reported by austin.f...@gmail.com, Oct 12 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36

Steps to reproduce the problem:
1. https://codepen.io/AustinFrance/pen/MEBXVj
2. Make sure scrolled to top of view so can see "Tests" title
3. Click on the Target column

What is the expected behavior?
Nothing obvious should happen.  Behind the scenes, the div that encapsulates the grid (header and content) is given focus (the one who's id is focusonme

What went wrong?
The view scrolls so that the clicked header is placed at the top of the page.  I am pretty sure this didn't used to happen as my regression tests for column sorting started failing because the header position had moved.

Did this work before? Yes 

Does this work in other browsers? No
 Same behaviour seen in Safari, behaves as expected in Firefox

Chrome version: 61.0.3163.100  Channel: stable
OS Version: OS X 10.12.6
Flash Version: 

If I remove tabindex="-1" from the LAST (clicked) header it doesn't scroll when clicked.



 
Cc: sc00335...@techmahindra.com
Components: Blink>Scroll
Labels: -Pri-3 Needs-Triage-M61 Triaged-ET M-63 OS-Linux OS-Windows Pri-2
Status: Untriaged (was: Unconfirmed)
Able to reproduce this issue on reported version 61.0.3163.100 and on latest canary 63.0.3239.0 using Windows 10, Ubunutu 14.04 and Mac 10.12.6 with steps mentioned in comment#0.

This issue is seen from M50[50.0.2166.0]. Hence considering this issue as Non-regression and marking as Untriaged.
Side note and correction (in case its relevant)
My regression tests were in fact failing because selenium+chromedriver were reporting the element as unclickable.  Recent versions have fixes in for that particular issue.

So the scroll behaviour itself didn't cause my test to fail, and may have been around longer than I originally thought.

Comment 3 by bokan@chromium.org, Oct 19 2017

Cc: bokan@chromium.org
Labels: Hotlist-Input-Dev Hotlist-Interop
Owner: sunyunjia@chromium.org
Status: Assigned (was: Untriaged)
A non-(recent)-regression, sunyunjia@, ptal to diagnose.
Sandra, any update on this?

Sign in to add a comment