- From: binoculars88 <notifications@github.com>
- Date: Tue, 02 Jun 2020 13:15:33 -0700
- To: w3c/pointerlock <pointerlock@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/pointerlock/issues/36/637781650@github.com>
@scheib our users started reporting a bug with pointerlock a few days ago. It seems it started around the 28th of May. Could this be related to the release of Chrome 83? A bit more info on the bug being reported: We have a window saying the pointer isn't locked when that's the case. When users click the window we request a pointerlock again. Never had any issues, but since a couple of days, users complain the window won't go away. We can't consistently reproduce this ourselves, but in the rare case where we see this too, we notice the function gets called but for some reason, the pointer doesn't lock. From that moment on, the Chrome tabs seems "broken" and even when refreshing in Incognito, pointerlock will always fail. Only trying it in a new Chrome tab locks the pointer again. We don't have a lot to go from atm, as we can't reproduce consistently, but I wanted the share this already. The bug is there for sure. We have a very active community, never had bug reports regarding this, but the last days it's one after the other. We haven't made any changes on our side. We will continue doing tests in the next couple of days. I'll keep you posted of we find something more concrete. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/pointerlock/issues/36#issuecomment-637781650
Received on Tuesday, 2 June 2020 20:15:45 UTC