Re: [w3c/pointerlock] feature request : Allow to set pointer position upon release (#61)

> A solution here needs to avoid this being usable to move the cursor to an arbitrary position by rapidly locking and unlocking the cursor.

Off the top of my head ```exitPointerLock``` can ignore the move if ```requestPointerLock``` is called outside of an isTrusted pointer down scope. That would require that to move the cursor the user starts the action with an interaction. This works for my example and @nadavsinai's drag examples while preventing arbitrary lock and move actions that might confuse a user.

Is there a use-case this doesn't account for?

As far as click-jacking I think @Paril is onto something. Most drag examples have the cursor starting and moving to the same area (some kind of working canvas with moving entities generally).

@hvanops Would these kind of solutions be acceptable? I'd like to get something working in browsers for at least the most common use-cases, so having caveats I think is workable to keep it simple.

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

Message ID: <w3c/pointerlock/issues/61/1806413146@github.com>