Re: [blink-dev] Intent to Prototype and Ship: Multi-Screen Window Placement: Fullscreen Companion Window

2022-05-23 Thread Mike Wasserman
Sure! Hopefully this explanation helps clarify that relationship: 1) Fullscreen companion window allows a frame with window-placement permission to request fullscreen on one screen, and open a popup window on another screen, from a single transient user activation. This enables a single click to

Re: [blink-dev] Intent to Prototype and Ship: Multi-Screen Window Placement: Fullscreen Companion Window

2022-05-23 Thread Mike Taylor
Hi Mike, can you help me understand the relationship of this work to Fullscreen capability delegation? Is the difference just 1 vs many screens? https://github.com/WICG/capability-delegation#allowing-fullscreen-from-opener-window-click On 5/9/22 8:35 PM, Mike Wasserman wrote:

Re: [blink-dev] Intent to Prototype and Ship: Multi-Screen Window Placement: Fullscreen Companion Window

2022-05-20 Thread Sean Voisen
Hi all — I'd just like to share a note of support for this enhancement to the API from Adobe and the Frame.io team. With the multi-screen window placement API, we can give users with multiple monitors the option to put the player on one monitor in full-screen, with media browsing and

Re: [blink-dev] Intent to Prototype and Ship: Multi-Screen Window Placement: Fullscreen Companion Window

2022-05-12 Thread Mike Wasserman
Hey Thomas, We don't necessarily need to change the web.dev article at this point, but following up to explore API progress and related enhancements (e.g. Fullscreen Capability Delegation ) might be valuable to developers. Let's

Re: [blink-dev] Intent to Prototype and Ship: Multi-Screen Window Placement: Fullscreen Companion Window

2022-05-10 Thread 'Thomas Steiner' via blink-dev
Hi Mike, As far as I understand, no developer-facing changes are introduced by this intent, so the article doesn't need changing, unless you want to mention feature detection and how this is in particular *not* detectable. Please advise. Cheers,