Files
orca/src/main
970d446d50 fix(browser): auto-grant pointerLock permission (#7697)
* fix(browser): auto-grant pointerLock permission

Orca's browser deny-by-defaults Chromium permission requests unless the
permission is in AUTO_GRANTED_BROWSER_PERMISSIONS. pointerLock is not in
that set, so immersive web apps (3D editors, FPS-style games) that call
requestPointerLock() get a confusing toast:

  "<url> asked for pointer lock, and Orca denied it."

with no in-app toggle to allow it.

Add 'pointerLock' to the auto-grant set. This mirrors the resolution of
the identical persistent-storage denial in #4801 / #4849. Chromium still
requires a user gesture before requestPointerLock() can engage, so this
only lifts Orca's application-level gate — it does not bypass the spec's
user-activation requirement.

* test(browser): cover pointer lock permission paths

Co-authored-by: Orca <help@stably.ai>

---------

Co-authored-by: Jinwoo-H <jinwoo0825@gmail.com>
Co-authored-by: Orca <help@stably.ai>
2026-07-10 09:42:10 -07:00
..
2026-07-09 21:54:22 -07:00
2026-05-30 02:46:28 -07:00
2026-05-30 13:09:17 -07:00