[w3c/pointerlock] Pointer Clip (#27)

This issue tracks the feature request for adding the ability to restrict where a pointer can be moved to.

Pointer Lock's initial capability hides the pointer and sends all mouse / touchpad movement data via MouseEvents without being restricted by e.g. screen boundaries.

The proposed Pointer Clip feature would keep the pointer visible, but restrict its motion. This would be useful primarily for games that include viewport navigation by 'pushing' onto the side of the game viewport. 

It is possible to restrict a pointer using Pointer Lock and drawing a pointer via the application. However, it results in additional input-to-display latency compared to restricting the motion of the system cursor.

This has been discussed before and is documented in Pointer Lock's  [Features to be considered for Next Version](https://github.com/w3c/pointerlock/blob/gh-pages/FeatureRequests.md#pointer-clip-limiting-movement-of-the-cursor-without-hiding-it)

It was also raised in https://github.com/whatwg/fullscreen/issues/99.


-- 
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/27