Regression: Unable to scroll 'Event Log' tab through mouse wheel on hovering the mouse over scrollbar.
Reported by
jshan...@etouch.net,
Apr 7 2016
|
|||
Issue descriptionChrome Version: 51.0.2702.0 (Official Build) 208b9d3c98bb3f1612ecc7c5e4abe49f8ea75210-refs/heads/master@{#385602} -32/64 bit. OS: Windows, Linux, Mac Steps: 1. Launch Chrome, open Dev-tool on NTP and go to Timeline section . 2. Reload the page, complete the recording and click on 'Event Log' tab. 3. Now try to scroll 'Event Log' tab by hovering the mouse over the scrollbar via mouse wheel and observe. Actual: Unable to scroll 'Event Log' tab through mouse wheel on hovering the mouse over scrollbar. Expected: Should be able to scroll 'Event Log' tab through mouse wheel on hovering the mouse over scrollbar. This is a regression issue broken in M-51, below is bisect info. Good Build:51.0.2686.0 Bad Build :51.0.2687.0 Narrow bisect: https://chromium.googlesource.com/chromium/src/+log/0b3847db495092eaeedf4b37b73f7784a3c12414..e233d14c7d5f89defc25a238157cdb58ca22e4d3?pretty=fuller&n=100 Suspecting: r382345 ? Please help to re-assign if your change is not the cause for this issue.
,
Apr 7 2016
I can reproduce this on Linux.
,
Apr 7 2016
This is another compositor hit test problem. Ian I tried your patch from the checker-boarding issue locally but it did not help the situation. If I avoid letting the compositor do the gesture handling for this event and allow it to go over to blink it appears to work correctly.
,
Apr 13 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/0b34eb5f70ea985690e856d6f58284835e629c75 commit 0b34eb5f70ea985690e856d6f58284835e629c75 Author: sunxd <sunxd@chromium.org> Date: Wed Apr 13 01:13:39 2016 cc: Scroll on main when possible incorrect hit testing hits scrollbar. As explained in crrev.com/238803005, it is possible that the composited layers have holes, if the point hits the first layer below the viewport point and the scrollbar layer, and the scrollbar layer is not an ancestor of the former layer, we should scroll on main, as shown below: 1) Should scroll on main: +--..... +----scroll_layer +----scrollbar_layer (<-viewport point hits this) +--.... +----....composited_unscrollable_layer (<-viewport point hits this) 2) Can scroll on impl: +--.... +----scroll_layer +----scrollbar_layer (<-viewport point hits this) +----....composited_unscrollable_layer (<-viewport point hits this) BUG= 601342 CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel Review URL: https://codereview.chromium.org/1878323002 Cr-Commit-Position: refs/heads/master@{#386880} [modify] https://crrev.com/0b34eb5f70ea985690e856d6f58284835e629c75/cc/trees/layer_tree_host_impl.cc [modify] https://crrev.com/0b34eb5f70ea985690e856d6f58284835e629c75/cc/trees/layer_tree_host_impl_unittest.cc [modify] https://crrev.com/0b34eb5f70ea985690e856d6f58284835e629c75/cc/trees/layer_tree_impl.cc [modify] https://crrev.com/0b34eb5f70ea985690e856d6f58284835e629c75/cc/trees/layer_tree_impl.h
,
Apr 13 2016
With the above change, the bug is fixed, please verify that. |
|||
►
Sign in to add a comment |
|||
Comment 1 by nyerramilli@chromium.org
, Apr 7 2016