[Bug]: Unknown permission: pointer-lock, keyboard-lock

[Aimless321]

Version

1.53.1

Steps to reproduce

import {chromium} from "playwright";

const browser = await chromium.launchPersistentContext('accounts/dev-account', {
    headless: false,
    permissions: ['clipboard-read', 'clipboard-write', 'pointer-lock', 'keyboard-lock'],
});

const page = await browser.newPage();

Expected behavior

Being able to launch chromium while granting websites permissions to perform keyboard lock and/or pointer locks.

Actual behavior

Chromium does not launch:

node:internal/modules/run_main:105
    triggerUncaughtException(
    ^

browserType.launchPersistentContext: Unknown permission: pointer-lock
Call log:

Additional context

These permissions are described here for chromium: https://developer.chrome.com/blog/keyboard-lock-pointer-lock-permission

Environment

System:
    OS: Linux 6.6 Manjaro Linux
    CPU: (8) x64 Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
    Memory: 6.71 GB / 15.51 GB
    Container: Yes
  Binaries:
    Node: 24.3.0 - ~/.nvm/versions/node/v24.3.0/bin/node
    Yarn: 1.22.22 - /usr/bin/yarn
    npm: 11.4.2 - ~/.nvm/versions/node/v24.3.0/bin/npm
  IDEs:
    VSCode: 1.84.2 - /usr/bin/code
  Languages:
    Bash: 5.2.37 - /usr/bin/bash
  npmPackages:
    @playwright/browser-chromium: ^1.53.1 => 1.53.1
    playwright: ^1.53.1 => 1.53.1

[Skn0tt]

Looks like we're missing permission mappings:

playwright/packages/playwright-core/src/server/chromium/crBrowser.ts

Line 441 in 8529ff0

const webPermissionToProtocol = new Map<string, Protocol.Browser.PermissionType>([

@Copilot please help us fix this. Here's where you can find the permission mapping in the CDP docs: https://chromedevtools.github.io/devtools-protocol/tot/Browser/#type-PermissionType
And here's a very similar PR you can draw inspiration from: #36186

[Skn0tt]

Wesley, could you elaborate on what kind of application you're testing? We can definitely add support for the permissions on a technical level, but i'm unsure whether the kinds of applications that use these permissions can be tested with Playwright anyways.

[Aimless321]

It's probably a very niche use case but i'm using the playwright libary for automating some actions in a browser game. So not really using the test part of playwright.

Interacting with it while in a keyboard / pointer lock seems to be working fine though!

[OnlineProxy-io]

You're probably getting that error because Playwright doesn’t support pointer-lock or keyboard-lock in its permissions array even though Chromium does. Playwright just doesn’t map those internally, at least not in v1.53.1, so throwing them in breaks the launch
The good news are, you don’t need to set those permissions manually anyway. If your script clicks or presses something like a real user would pointer and keyboard locks kick in just fine. So just delete pointer-lock and keyboard-lock from the list and move on. Gonna still work
If you're really itching to control it yourself you can mess with context.newCDPSession() and call Browser.grantPermissions directly, just use pointerLock and keyboardLock (camelCase) instead. But tbh most of the time it's not worth the hassle