+domlaskowski
Is this something you can take a look?

mukai: could this be related to the new cursor shape protocol?

Thanks for reporting, looks like related to my changes, yet I still can't reproduce the issue on my local environment.

Question: does this happen on any Android apps? Like, does this also happen on Play Store?

Question 2: when this happens, is the app working? Like, does the app respond to keyboards or mouse-clicks?

The app that I recorded (CrossOver) is an Android app.  The part of CrossOver that you see in the video is a full android app, without any wine processes running.  I have not seen it on the Play Store, but I think that is more due to me rarely using the Play Store.  

My co-worker has also seen this bug on more than one Android app (including CrossOver) but he could not recall which other app he was using.  

He also reports that alt-tabing to get the focus away from the app and back to it will fix the problem (for him).  

When this is happening, the app will not respond to the mouse clicks (as far as I could tell).  It seems to me to be behaving as if the mouse is behind the window instead of in front of it.   

Great, thanks for the info. Next question (sorry asking so many): does your co-worker use the same chromebook or a different device?

Note that the mouse itself should be on the app, even though it becomes invisible. No-response on click (i.e. looks like cursor moves behind the app) means that the app is not working well -- I guess the app (or some underlying system?) is suspended for some reasons?

That said, use of invisible cursors on such situation is very weird, maybe we might want to change that behavior.

I just realized that while CrossOver is a plain Android app, the screen in question is an automated software installer for Wine applications, so it is likely to have been "underneath" a Wine window immediately prior to this weird behavior being triggered.  (We haven't confirmed for sure that this is the only situation where this can happen.)

But, if you say that the window with the invisible mouse is probably suspended, could something have changed to cause this?  The Wine window closes itself and actually exits the Unix process hosting that Activity when the Windows app quits.  I wonder if the window underneath in that situation used to get onResume() but no longer does.

To clarify: Comment #10 is my co-worker, and we were using different devices.