Mobile emulation randomly exhibits desktop cursor
Reported by
teo8...@gmail.com,
Nov 6
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36 Steps to reproduce the problem: 1. open the Developer Tools 2. enable mobile emulation 3. go to some website What is the expected behavior? Should always have the "fake finger" round cursor emulating a touch screen. Under no circumstances should it ever display normal cursors like an arrow, a text caret or a link pointer (hand). No matter whether there's something wrong in the page contents, css, or javascript (which I don't think is the case anyway), such cursors don't exist on touch devices, actually no cursor exists, so only the "finger" emulation cursor should show up. What went wrong? At random times, when emulating mobile, I get the desktop cursors. And even the wrong ones, e.g. an arrow or text caret over links instead of the pointer/hand. I don't know what triggers this, I observe it in an utterly random fashion. Unfortunately I can't share some urls that seem to trigger this more often, as they are private. I'm so sick of this kind of issues. Did this work before? Yes recently Chrome version: 70.0.3538.77 Channel: stable OS Version: Flash Version:
,
Nov 8
Able to reproduce the issue on the reported chrome 70.0.3538.77 latest chrome 72.0.3604.0 using Windows 10, Mac 10.14.0 and Ubuntu 17.10. Below is the bisect information for same. Bisect Info: ================ Good build: 69.0.3455.0 Bad build: 69.0.3456.0 CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/e6c18518bbcc4fb0ca88aa7d11214021abad09d9..a1403ff3efbd8f412e2e0c9b0257da3933f8692b Suspect: https://chromium.googlesource.com/chromium/src/+/a1403ff3efbd8f412e2e0c9b0257da3933f8692b Reviewed-on: https://chromium-review.googlesource.com/1069661 dgozman@chromium.org: Please confirm the issue and help in re-assigning if it is not related to your change. Note: As Dev OOO Nov 6 - 26, 2018. Hence assigning to reviewer. Thanks!
,
Nov 8
This was known at the time of refactoring, should only happen with OOPIFs on the page. Downgrading to P2 priority, over to wjmaclean@ for triage. |
|||
►
Sign in to add a comment |
|||
Comment 1 by viswa.karala@chromium.org
, Nov 7