Does pressing shift once help? Does this happen all the time? Sounds like a intermittent problem, since I cannot reproduce locally.

It does not help.  However, I find that if I click and hold down the left mouse button outside of the emulation area and drag into the emulation area, I am able to at least see my arrow cursor, that is, until I let go of the mouse button; then it disappears again and I must move my cursor outside of the emulation area to see it.

Sounds pretty bad. Unfortunately, we need a repro scenario to find the problem here.

Did you experience any cursor problems other than this one?

chrome version : 52.0.2743.116 m
os: windows 10 (1607)

i have the same issue whatever i reinstall the system or install low version chrome cannot solve this issue, but in other machines same os and chrome version is working

in desperation i find a way to show grey dot bu is not a long-term solution

control panel->hardware and sound->mouse->pointer options->display pointer trails

@dockeryz: Could you please respond to the comment #3 and update the bug accordingly.

Thank you.

I'm not sure how to replicate this.  This happened after the version 50 update.  Do you need a screenshot?  Is there a setting in chrome://settings that I need to set?

Hey thought id add some additional information to this ticket:

Firstly, i can reproduce this issue however it appears to only happen on a particular brand on monitor (thought I cant confirm otherwise)

Details:
OS: Windows 10
Chrome: Version 52.0.2743.116 m (64-bit)
GFX: Nvidia GTX 960m (Driver version: 353.82)

Attached are 2 videos:

1. on Laptops inbuilt screen (works correctly) 
Video: https://drive.google.com/open?id=0B_aV_-3uzUiIYjNSS3RpMUhOaUU

2. on 2nd monitor plugged in via HDMI, (ACER G257HL), doesnt display correctly
Video: https://drive.google.com/open?id=0B_aV_-3uzUiISEF5UDVDLWlDVVk

Curious note: I tried to record this issue using snagit, while recording the cursor was not present (on the acer), but was displayed in the outputted video, as in the grey circle is there as it is supposed to be (What the?), so I have used my phone to record the videos so you can see the issue.

Cheers,

Mitch

OK, so i kinda got stubborn, and delved deeper into this issue.


Turns out the laptop was in fact using the intel gpu instead of the nvidia one.

i jumped through the settings an found Quantization Range settings in advanced for the screen, it was set to Default, changed it to Full Range, and this resolved the issue.


please see attached screenshot :)

Deleted: Fix for missing cursor.png 862 KB

	Fix for missing cursor.png 862 KB View Download

OK, so even more... :\

it appears to be the act of triggering the Full Range that "fixes" it.

however on reboot, despite the setting being retained, it no longer works, you need to toggle default then back to full range again to "fix" it again.

I am able to reproduce your solution too!  Awesome!
I haven't yet rebooted my computer to see those results, but I don't care, I can QA on my large screen now!

Thank you!

My monitor information is this FWIW:

          Card name: Intel(R) HD Graphics 520
       Manufacturer: Intel Corporation
          Chip type: Intel(R) HD Graphics Family
           DAC type: Internal
        Device Type: Full Device
         Device Key: Enum\PCI\VEN_8086&DEV_1916&SUBSYS_06DE1028&REV_07
     Display Memory: 4162 MB
   Dedicated Memory: 128 MB
      Shared Memory: 4034 MB
       Current Mode: 1920 x 1080 (32 bit) (59Hz)
       Monitor Name: Generic PnP Monitor
      Monitor Model: LG TV
         Monitor Id: GSM0001
        Native Mode: 1920 x 1080(p) (60.000Hz)
        Output Type: HDMI

Happy to help :)

Looks like there was a investigation and fix by mitchelltrent@.  Marking issue as resolved.  Thanks for sharing!

And thanks to dockeryz@ for the report.

Fix described by mitchelltrent@ worked for me.

This issue is marked as Fixed, but it is NOT. I'm getting it in version Version 54.0.2840.59 m (64-bit) with Intel(R) HD Graphics 530 Video.

The action of changing Quantization range described above fixes it until the next time desktop is locked and then the same action has to be dome over again. It is extremely annoying for someone who has to work with mobile emulation.

The workaround described above does NOT fix the issue it is merely a temporary workaround until the next screen lock.

Sorry for multiposting.

I've been having the same issue for a while now. It used to work fine, showing a grey dot where the pointer was. Now I see nothing and must interact blindly.

Chrome 54.0.2840.100
Nvidia GTX960 370.28
Archlinux
AwesomeWM

I have same issue. Mouse and keyboard connected to monitor`s USB ports. Monitor connected to notebook by HDMI and by USB to make monitor`s USB ports work. 

Reconnecting mouse and keyboard to notebook and disconnecting monitor from notebooks USB does not help.

I still have this issue. This is not fixed for me, and it should be reopened. 
I can't try the fix, since I'm on a remote workstation and don't have Intel HD graphics installed.

A temporary workaround for this is enabling 'Add device type', then setting the device to 'Responsive' and then change the device type to 'Mobile (no touch)'.

From these recent comments it sounds like changing the quantization setting isn't a full, persistent fix.  I'll try again to repro on some other Intel-graphics hardware.

For those who've found this working before, do you happen to know the version when it worked / started breaking?  A range would be helpful.

I still have this issue as well.

I'm also facing this issue on version 58.0.3029.41 beta (64-bit) in Windows 7 Pro.

UPDATE: I just realized the touch cursor is visible on my laptop with the Intel Quantization Range set to Default. The touch cursor is only missing in the desktop monitor connected to my laptop via HDMI cable (output set to extended desktop).

Setting the Quantization Range to Full fixed the missing touch cursor on the desktop for a period of time, but after a reset (or maybe I just logged off, can't remember) the cursor is missing again even with Quantization Range set to Full.

 Issue 714441  has been merged into this issue.

this is my config:  chrome version 58.0.3029.110 (64-bit).  win10
need to set again the quantization range to workaround everyday getting back to work.  hope to see a fix from google.  thanks.

Problem of disappearing touch pointer in device Development Console. Config:

Chrome 60.0.3112.113
Windows 7 64 SP1
Intel i5-6500 based Intel 530 Graphics with 2 monitors (1 DP and 1 VGA) connected

same issue, for some reason only on second display.
both displays are Display Port with VGA adapter.
if i set the Quantization Range it becomes visible on both.

Chrome: 61.0.3163.100 (Official Build) (64-bit)
Windows: 10 version 1703 (os buid 15093.608)
Intel i5-7500 with HD Graphics 630

I'm also experiencing this on a multi-monitor setup with an Intel HD Graphics chip on Windows 7. The Quantization Range setting workaround resolved it for me, but I haven't rebooted yet...


Seems related to and/or a duplicate of this other issue:
https://bugs.chromium.org/p/chromium/issues/detail?id=656915

The Quantization Range workaround resolution did not persist after rebooting. Had to toggle it to Default and back to Full Range for the cursor to show again.

Intel indicates that the PC already has the latest driver installed for the Intel(R) HD Graphics 530 chipset within.

replay: Comment 5 by chen3002...@gmail.com, Aug 7 2016

It's work. Thanks