Issue metadata
Sign in to add a comment
|
Mouse Offset in 3D Environment
Reported by
kga...@uifoundry.com,
Nov 7
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36 Steps to reproduce the problem: 1. Reduce browser zoom <100% 2. Load interactive element into 3D Environment ie. YouTube, PDF 3. Mouse is offset from control What is the expected behavior? Mouse should not be offset in 3D Environment What went wrong? Mouse is not offset in 3D Environment when Browser Zoom is set to 100% Did this work before? N/A Chrome version: 70.0.3538.77 Channel: stable OS Version: 10.0 Flash Version: We have a private shareable URL to reproduce this problem
,
Nov 8
,
Nov 8
kgaree@ Thanks for the issue. Request you to provide a URL where this issue can be reproduced, which will help in further triaging. Thanks..
,
Nov 12
As per the test URL provided by the reporter over mail, sent a reply back to the reporter with the observations.
,
Nov 15
Able to reproduce this issue on Mac OS 10.13.6, Windows 10 and Ubuntu 17.10 on the reported version 70.0.3538.77 and latest Canary 72.0.3610.0 as per the test URL provided by the reporter over mail. Bisect Information: =================== Good Build: 65.0.3318.0 Bad Build : 65.0.3319.0 By running per-revision script below unable to get the ChangeLog URL as all bad builds are invoked. Tried increasing the good build range, but still all bad builds are getting invoked. https://chromium.googlesource.com/chromium/src/+log/65.0.3318.0..65.0.3319.0?pretty=fuller&n=10000 From the above Changelog, unable to find the right suspect. Tentatively adding 'Blink>Compositing>Transform3D' component, marking this issue as Untriaged and requesting the appropriate Dev team to look into the issue and help further. Thanks..
,
Nov 15
From the provided revision range, I'm tentatively assigning this to malaykeshav@chromium.org, due to this CL: https://chromium.googlesource.com/chromium/src/+/b41800a722fbb3d4213e2a5ee517079470922822 If I'm wrong, and you don't know a better candidate owner, go ahead and put back to untriaged.
,
Nov 16
,
Dec 10
,
Dec 18
The change in #6 only effects Chrome OS. Looking at the changelog, I would suspect something related to events. Maybe https://chromium-review.googlesource.com/c/chromium/src/+/859784/ or https://chromium-review.googlesource.com/c/chromium/src/+/855198/
,
Dec 18
susan.boorgula@, it sounds from c#5 that you are able to reliably reproduce this problem, based on private information you received from the reporter? I don't quite understand the second part of your comment there, but is it possible for you to bisect this further within the range, down to a single commit? Otherwise, we're just guessing at a candidate. Also, once we find the suspect CL, we'll need to get the URL to reproduce the problem over to the suspect CL owner.
,
Dec 19
Tried testing the issue on Windows 10 and Mac OS 10.13.6 on the latest Canary 73.0.3645.0 by navigating to the URL provided over email, but somehow unable to find any content in it now. Hence unable to reproduce the issue and bisect this further. kgaree@ Request you to check the Email regarding this issue and update accordingly, which will help in further triaging. Thanks..
,
Dec 19
,
Jan 2
The NextAction date has arrived: 2019-01-02
,
Jan 2
kgaree@, please provide input if possible. I'm setting the next action date for 2 more weeks, after which we'll likely close this bug.
,
Jan 16
(6 days ago)
The NextAction date has arrived: 2019-01-16
,
Jan 16
(6 days ago)
Closing for no action. Please re-open if you can provide the needed input. Thanks. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by kga...@uifoundry.com
, Nov 7