[w3c/pointerlock] Proposal to integrate pointer lock with the permissions API (Issue #94)

We (on the Chrome team) are working on putting pointer lock and keyboard lock behind permission prompts ([Chrome Platform Status](https://chromestatus.com/feature/5142031990259712)). 

One piece of feedback that we got from a first-party developer that uses keyboard lock is that they'd like to have the permission state exposed via the [permissions API](https://www.w3.org/TR/permissions/) so that they can update their UI according to the permission state. We believe the same use case applies to pointer lock.

The pointer lock API spec [mentions](https://www.w3.org/TR/pointerlock-2/#security):

> User agents may prompt for confirmation before locking, this preference may be saved as a content setting.

but does not mention the permissions API. We propose to add a section about integrating with the permissions API, similarly to how other APIs such as [window management](https://www.w3.org/TR/window-management/#api-permission-api-integration) do.

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

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

Received on Wednesday, 8 May 2024 04:15:08 UTC