Transient incorrect transform for multi-display cursor |
||
Issue descriptionWhen dragging a window across displays with different densities or rotations, the cursor has an incorrect transform for a frame or two after crossing the display boundary, because the new bitmap is captured asynchronously after Ash initializes the cursor to the old bitmap.
,
Sep 28
Triage nag: This Chrome OS bug has an owner but no component. Please add a component so that this can be tracked by the relevant team.
,
Sep 28
|
||
►
Sign in to add a comment |
||
Comment 1 by osh...@chromium.org
, May 16 2017