Re: [w3c/pointerlock] Feature Request: Allow for a pointerevent-scoped pointerlock with less restrictions (Issue #81) from Mustaq Ahmed on 2022-12-05 (public-webapps-github@w3.org from December 2022)

From: Mustaq Ahmed <notifications@github.com>
Date: Mon, 05 Dec 2022 06:53:09 -0800
To: w3c/pointerlock <pointerlock@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/pointerlock/issues/81/1337518817@github.com>

Is the [Pointer Capture](https://www.w3.org/TR/pointerevents/upcoming/#pointer-capture) support in this spec not enough for this use-case?  You can [request a pointer capture](https://www.w3.org/TR/pointerevents/upcoming/#setting-pointer-capture) on `pointerdown` which will get [released implicitly](https://www.w3.org/TR/pointerevents/upcoming/#implicit-release-of-pointer-capture) on `pointerup`.

One difference here is that the mouse cursor remains visible in Pointer Capture (unlike PointerLock API).  Perhaps an option to hide the cursor on Pointer Capture is all you need?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/pointerlock/issues/81#issuecomment-1337518817
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/pointerlock/issues/81/1337518817@github.com>

Received on Monday, 5 December 2022 14:53:21 UTC