Issue metadata
Sign in to add a comment
|
Node highlighting doesn't work when rAF aligned input is enabled |
||||||||||||||||||||||
Issue description1) Launch chrome with RafAlignedInput for mouse. 2) Set a DOM Event Listener for Mouse Move 3) Try the element picker to select a node. 4) Notice the nodes don't highlight. Repeat same steps with RafAlignedInput disabled. It works. Appears to be related to the nested event loop that occurs while you are inside a begin main frame.
,
Oct 26 2016
,
Oct 26 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/c946754cb3f792ed4f5cc51ec3ba468442130359 commit c946754cb3f792ed4f5cc51ec3ba468442130359 Author: dtapuska <dtapuska@chromium.org> Date: Wed Oct 26 21:11:45 2016 Remove complexity from the input pipeline. Mouse Move events are sent right away. Remove the acking behaviour devtools implemented to get around the single mouse move event outstanding. This code is unnecessary now. BUG=615090, 659289 Review-Url: https://codereview.chromium.org/2453663002 Cr-Commit-Position: refs/heads/master@{#427790} [modify] https://crrev.com/c946754cb3f792ed4f5cc51ec3ba468442130359/content/renderer/devtools/devtools_agent.cc [modify] https://crrev.com/c946754cb3f792ed4f5cc51ec3ba468442130359/content/renderer/input/render_widget_input_handler.cc [modify] https://crrev.com/c946754cb3f792ed4f5cc51ec3ba468442130359/content/renderer/input/render_widget_input_handler.h [modify] https://crrev.com/c946754cb3f792ed4f5cc51ec3ba468442130359/content/renderer/render_widget.cc [modify] https://crrev.com/c946754cb3f792ed4f5cc51ec3ba468442130359/content/renderer/render_widget.h
,
Oct 31
Bulk closing low-priority issues with no activity. Please re-file and refer to the closed issue if it's essential to fix. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by dtapu...@chromium.org
, Oct 25 2016