New issue
Advanced search Search tips

Issue 620309 link

Starred by 5 users
Status: Assigned
Owner:
sahel@chromium.org
Cc:
flackr@chromium.org
tdres...@chromium.org
bokan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocked on:
issue 125223


Sign in to add a comment

Keyboard scrolling stops working when clicked DOM node is being removed

Project Member Reported by surma@chromium.org, Jun 15 2016 
Version: 51.0.2704.84
OS: OS X

What steps will reproduce the problem?
https://output.jsbin.com/xaluti

What is the expected output?
Keyboard-based scrolling should continue working.

What do you see instead?
It doesn’t.

Comment 1 by flackr@chromium.org, Jun 15 2016

Cc: tdres...@chromium.org
Components: Blink>Input Blink>Scroll
Looks like we target scroll at the m_mousePressNode (https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/input/EventHandler.cpp?sq=package:chromium&dr&rcl=1465975119&l=509) which is only set on mouse press. We should retarget this when the element is detached to its parent / containing block.

Comment 2 by dtapu...@chromium.org, Jun 16 2016

Labels: Hotlist-Input-Dev
Owner: bokan@chromium.org
Status: Assigned (was: Untriaged)

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

Cc: bokan@chromium.org
Owner: sahel@chromium.org
I think this is analogous to the touch and wheel cases so over to sahel@

Comment 4 by sahel@chromium.org, Oct 25

Blockedon: 125223
This is fixed for gesture scrolling (touch/wheel scrolling)
Blocking on crbug.com/125223 since this will be a no issue once keyboard scrolling is also handled by gesture scrolling.
►

Sign in to add a comment