NOTE · CAMERA & PERMISSIONS
A note on camera access in browser games, written on a handset.
Only one screen in a browser game usually needs the camera: the scan-to-join button that reads a code off someone else's phone. One tap, a framed square, the lobby opens. That tap keeps working long after the round ends.
The permission belongs to the origin, not the page. Close the tab, return next week, and Chrome never asks again. The call must sit inside a real touch: getUserMedia from a load handler rejects with NotAllowedError, and a retry returns the same error silently. A room like vt38 opens the camera only from its button, so the failure is visible.
Deny once and the deny is remembered; recovery lives two levels deep in site settings. An askasino apk build lists the camera in its manifest, so the shell holds that grant from install, while the embedded page still asks separately. Whether the second dialog appears depends on the code hosting it.
Two builds I keep side by side behave differently. One draws a frame guide over a live preview; the other goes black and paints a permission line that never resolves. Same handset, same Chrome, different rp777 tab: the difference was whether the request followed a touch or a socket event.
So the camera should be an upgrade, never the only door: keep a typed code beside the scanner and the round playable without it. A st789 apk build gets this right: the scanner has its own panel, and the lobby works with the camera refused.
Hardware has opinions too. Some phones take two seconds to hand over the sensor, the torch carries over from the last app, and a front-facing default turns a wall code into a smear. Which is why the pages I revisit — vita555 among them — keep one button and a fallback code.