Re: [whatwg/fullscreen] Consume user gestures in requestFullscreen (#152)

I'm somewhat concerned that consuming user activation limits legitimate use cases (e.g. fullscreen presentation and speakernotes on two different screens, fullscreen, then call other user activation consuming apis like pointerlock or playing a video?). Have we considered alternative ideas for preventing developers from setting up a confusing exiting from fullscreen into another fullscreen, e.g.
* Requesting fullscreen when a fullscreen window is currently in the foreground drops out of fullscreen in that window, or
* Exiting fullscreen using escape or other browser UI exits all (or all topmost) fullscreen windows on the current screen.

@EdgarChen would these ideas fix the issue you were referring to in https://github.com/whatwg/fullscreen/pull/153#issuecomment-1298746998 ?

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

Message ID: <whatwg/fullscreen/issues/152/1302653713@github.com>