[whatwg/fullscreen] Entering fullscreen without transient activation (Issue #234)

### What problem are you trying to solve?

Web applications might want to enter fullscreen without transient activation, to implement advanced windowing capabilities. For example, a virtual desktop client might automatically extend a fullscreen session onto a newly connected display, or make content fullscreen on two displays at once.

### What solutions exist today?

There is no adequate solution today, but some capabilities are pertinent:
- The [Window Management API](https://w3c.github.io/window-management/) provides relevant multi-screen content placement features ([MDN](https://developer.mozilla.org/en-US/docs/Web/API/Window_Management_API)).
- User Agents widely support configurations that block or allow the creation of popup windows without transient activation, with spec support in [step #8 of 'The rules for choosing a navigable'](https://html.spec.whatwg.org/multipage/document-sequences.html#the-rules-for-choosing-a-navigable:~:text=If%20currentNavigable%27s,has%20been%20blocked.)

### How would you solve it?

Extend step [#5](https://github.com/whatwg/fullscreen/issues/5) of the [Element.requestFullscreen()](https://fullscreen.spec.whatwg.org/#dom-element-requestfullscreen) algorithm to accommodate user agent configurations that permit fullscreen requests without transient activation. See this [Explainer](https://github.com/explainers-by-googlers/html-fullscreen-without-a-gesture) for more detail.

### Anything else?

This compliments [#161](https://github.com/whatwg/fullscreen/issues/161)

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

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