Re: [w3c/pointerlock] Feature Request: Allow for a pointerevent-scoped pointerlock with less restrictions (Issue #81)

I’m running into the same issue as OP, although in a somewhat different context. I’d like to use Pointer Lock for something similar to the [Jog movement over spinner controls](https://w3c.github.io/pointerlock/#jog-movement-over-spinner-controls) use case described in the spec. Just as OP found, the browser notification about the cursor being captured is very disruptive and unfortunately makes the API not so useful for microinteractions like this.

I will likely also end up using Pointer Capture, but would very much prefer Pointer Lock’s behavior at the edge of the screen and not moving the user’s cursor while locked.

I like OP’s suggestion of a less disruptive locking method that’s guaranteed to exit lock on pointerup. A less ideal alternative that would at least help but that doesn’t require adding new methods to the API could be for user agents to defer showing the warning until the pointer has been locked for some amount of time, say 5 consecutive seconds. That way, short interactions are unimpeded, but if a pointer is locked for long enough that a user might get confused, it shows the notification.

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

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