New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 718148 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: ----
Type: ----



Sign in to add a comment

[Component Request] Blink>Input>PointerLock

Project Member Reported by chongz@chromium.org, May 3 2017

Issue description

1] Component Name: Blink>Input>PointerLock

2] Parent Component (e.g. Blink, UI>Browser, etc...): Blink>Input

3] Description of Component: Pointer Lock (MouseLock in PPAPI) related to the https://github.com/w3c/pointerlock specification: document.body.requestPointerLock and mouse events including movementX & Y.

4] Admin/ Owner: dtapuska@chromium.org

5] Please specify what triage practices will be followed for the component
(i.e. what team will do it and how frequently).
input-dev will do the weekly triage.

The original component IO>PointerLock is confusing as PointerLock is not a physical device like mouse or keyboard. Web platform related features should be tracked under Blink.

We'd like to rename IO>PointerLock to Blink>Input>PointerLock, or have IO>PointerLock removed and I will bulk move the bugs.


 
Owner: lafo...@chromium.org
Status: Fixed (was: Untriaged)
Done.

Sign in to add a comment