Pointer Lock 2 API, some new features

[Van Catha]

We have been dealing with using chrome to provide a remote desktop experience, now with google stadia around the corner there are still some key features lacking in chromes Pointer Lock / event handling.

#1 Pointer Lock cannot show the cursor while keeping the cursor inbounds, this is a hard requirement for responsive RDP.
#1.1 Pointer Lock should also be able to lock the cursor inbounds + show it without going full screen.

##1 To be clear this allows a client side hardware cursor to be rendered but kept inbounds of an element, very important for remote software that requires edge panning.

#2 navigator.keyboard.lock() only works in FullScreen mode.  In a non-fullscreen mode there is no way to set a keyboard.lock() on an element, this results in for example losing your tab if you accidentally press Ctrl+W, which for stadia is very common in first person shooter games.

#3 And of course a long known issue, mouse movement events are delayed around 1-2 frames, and stall the render loop.  But this is not really related to Pointer Lock, more event handling.

I am wondering if this is the right place to discuss features, I am looking to eventually push some of these to the w3c groups after discussion.

WDYT!

[Reilly Grant]

The issue tracker for the Pointer Lock API is the right place to propose and discuss these new features.

Reilly Grant | Software Engineer | rei...@chromium.org | Google Chrome

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/1f12ee6e-791b-4d83-b4d9-b224d319b889%40chromium.org.