Re: [whatwg/fullscreen] Consume user activation in `element.requestFullscreen()` (#153)

I guess it depends on what features/API calls follow a call to `.requestFullScreen()`... I see there is mention of Pointerlock in the bug and Screen Orientation Lock is another.  

I'm simultaneously hoping we can prevent the Screen Orientation API (which depends on FS API) from arbitrarily changing the screen orientation [without a user gesture](https://github.com/w3c/screen-orientation/pull/218). 

If you have an Android device handy, try this out in Chrome: 
https://marcoscaceres.github.io/playground/annoying.html 

(if you can't try it out, it loops rapidly changing the screen orientation making it difficult of users to access the browsers UI - you need to either turn off the screen or quickly swipe from the bottom to stop it). 

I personally don't think the above behavior should be acceptable for any API to do on the Web. So, I was hoping we wouldn't consume the user activation in FS API, but rather have the Screen Orientation API consume the user activation. 

Alternatively, we could have it consume the user activation if #186 was in place, all in one go. The advantage being that it wouldn't breaking any sites that are depending on FS API to not consuming the user activation.

For pointerlock, maybe a solution like #186 could also work. You request them all at once, and exiting fulls screen releases all the locks. 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fullscreen/pull/153#issuecomment-1298217849
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fullscreen/pull/153/c1298217849@github.com>