Revert "Keep scroll by keyboard after child focused node is removed"
This reverts commit 09a1f53e. Sheriff: I suspect this is causing the LEAK failures here: https://ci.chromium.org/p/chromium/builders/ci/WebKit%20Linux%20Trusty%20Leak/34655 https://test-results.appspot.com/data/layout_results/WebKit_Linux_Trusty_Leak/34655/webkit_layout_tests/layout-test-results/results.html Original change's description: > Keep scroll by keyboard after child focused node is removed > > So far, scroll stops if focused child node is removed > while scrolling parent node. > This is because the event handler passes the |MousePressNode|. > If focused child node(|MousePressNode|) is removed, > it will be null and scrollable area changed to document. > > |LogicalScroll| finds scrollable area from |MousePressNode|. > If we save this scrollable area node, > we can get one more chance to find proper node to scroll. > > > Bug: 493078 > Change-Id: I6e81ca0a0d15e0def66c8457840ca9e1343e8dba > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1611620 > Commit-Queue: Lan Wei <lanwei@chromium.org> > Reviewed-by: Lan Wei <lanwei@chromium.org> > Reviewed-by: David Bokan <bokan@chromium.org> > Cr-Commit-Position: refs/heads/master@{#663040} TBR=bokan@chromium.org,lanwei@chromium.org,bluewhale.marc@gmail.com Change-Id: I4b8ea440dc16022077746d7924506e7f03ac1673 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 493078 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628880Reviewed-by:Mason Freed <masonfreed@chromium.org> Commit-Queue: Mason Freed <masonfreed@chromium.org> Cr-Commit-Position: refs/heads/master@{#663102}
Showing
Please register or sign in to comment