Mike Wasserman

To more concretely answer your questions, as they pertain to Chromium's current implementation: > Is it a command line flag or similar that would be enabled in kiosk mode and...

Thanks, @foolip! I'll file a spec issue for permissions API support soon. An [alternative](https://github.com/explainers-by-googlers/html-fullscreen-without-a-gesture/blob/main/README.md#considered-alternatives) and [separate explainer](https://github.com/w3c/window-management/blob/main/EXPLAINER_initiating_multi_screen_experiences.md) considered multiple operations per gesture, but that indeed fails application-driven use cases, while...

The explainer now includes [Permissions API integration](https://github.com/explainers-by-googlers/html-fullscreen-without-a-gesture?tab=readme-ov-file#permissions-api-integration). Using that [Permissions API](https://www.w3.org/TR/permissions/) signal and HTML's definition of [transient activation](https://html.spec.whatwg.org/multipage/interaction.html#transient-activation) (which is web-exposed via [The UserActivation interface](https://html.spec.whatwg.org/multipage/interaction.html#the-useractivation-interface)), seems beneficial for spec clarity,...

The explainer has a relevant [section](https://github.com/WICG/manifest-incubations/blob/gh-pages/borderless-explainer.md#opening-a-popup-from-a-borderless-pwa): > Opening a popup from a borderless PWA > - Opening a popup to any other origin → The popup should NOT be in...

This seems like it would be a clear win for screen orientation API ergonomics, but I'm curious about the premise: `The above assumption is wrong, because .unlock() IPC SHOULD notify...

Returning a promise seems nice, but the spec might need to note they are best-effort? AFAICT: 1) OSes may lack success/failure signals, or delay honoring requests (e.g. activity backgrounded) 2)...

Would this break entering fullscreen and locking orientation with one activation if requestFullscreen consumes the gesture per https://github.com/whatwg/fullscreen/pull/153 ?

Thanks for your work here, @marcoscaceres. We should absolutely prevent abuse akin to your compelling [example](https://github.com/w3c/screen-orientation/pull/218#issuecomment-1290029378). The most apparent risk is breaking uses of Element.requestFullscreen() and Screen.Orientation.lock() from one transient...

While I'm agnostic to the method used, it does seem potentially useful to expose a 'can probably lock' signal. Based on my novice reading of underlying OS APIs, user agents...

That's a reasonable line of inquiry, presumably to protect users against abusive sites. Would you suggest consuming or simply gating on a transient activation signal? IIUC, sites can currently request...