New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 872784 link

Starred by 0 users
Status: Assigned
Owner:
malaykeshav@chromium.org
Cc:
adlr@chromium.org
seobrien@chromium.org
sahel@chromium.org
mustaq@chromium.org
malaykeshav@chromium.org
█ puneetster@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

mouse cursor position offset from click

Project Member Reported by seobrien@chromium.org, Aug 9 
Chrome Version: 69.0.3478.0 dev
OS: 10834.0.0 (Official Build) dev-channel nautilus test

Mouse cursor position (via touchpad) is off by 3 or 4 mm.  Coordinates of what is being drawn (mouse cursor) is 3/4 mm away (higher) from where the click is being registered.  Interestingly enough Android app dialogs seem to click okay. Touch screen seems okay.

https://listnr.corp.google.com/report/85591912248

Comment 1 by seobrien@chromium.org, Aug 9

Cc: puneetster@chromium.org adlr@chromium.org
Components: UI
Labels: OS-Chrome
Owner: ccameron@chromium.org
Found a similar issue on MacOS:
https://bugs.chromium.org/p/chromium/issues/detail?id=860344

ccameron@, do you think this could be related to the cursor offset bug you fixed for macOS?

Comment 2 by seobrien@chromium.org, Aug 9

Cc: seobrien@chromium.org

Comment 3 by ccameron@chromium.org, Aug 9

Owner: ----
Unlikely that this is the same as  issue 860344  -- that issue only affects macOS (and is deep in mac-specific code).

Comment 4 by seobrien@chromium.org, Aug 9

Cc: sahel@chromium.org mustaq@chromium.org
+Blink Input people

Comment 5 by lhchavez@chromium.org, Aug 10

Components: -UI UI>Input

Comment 6 by afakhry@chromium.org, Aug 10

Cc: malaykeshav@chromium.org

Comment 7 by afakhry@chromium.org, Aug 20

Owner: malaykeshav@chromium.org
Malay, please triage this.

Comment 8 by malaykeshav@chromium.org, Aug 20 

Does disabling enable-viz-hit-test-draw-quad in chrome://flags fix the issue?

Comment 9 by puneetster@chromium.org, Aug 21 

I will try this the next time I hit this issue.  I don't have exact repro steps.

Comment 10 by benhenry@google.com, Jan 11

Status: Assigned (was: Untriaged)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.
►

Sign in to add a comment