From 1f3e05c7e50f46b68cb1612b776927971364727b Mon Sep 17 00:00:00 2001 From: Brad Triebwasser <103072903+bradtriebwasser@users.noreply.github.com> Date: Tue, 29 Aug 2023 22:31:55 +0000 Subject: [PATCH] Add Fullscreen popups explainer and related doc (#140) SHA: b439243a561534e176edfc893a2d5cecc72db345 Reason: push, by michaelwasserman Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> --- index.html | 92 +++++++++++++++++++++++++++--------------------------- 1 file changed, 46 insertions(+), 46 deletions(-) diff --git a/index.html b/index.html index 1ff0dd1..7e977a9 100644 --- a/index.html +++ b/index.html @@ -5,10 +5,10 @@ Window Management - + - + - - +

Window Management

-

Editor’s Draft,

+

Editor’s Draft,

More details about this document
@@ -725,7 +725,7 @@

Publication as an Editor’s Draft does not imply endorsement by W3C and its Members. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.

This document was produced by a group operating under the W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.

-

This document is governed by the 2 November 2021 W3C Process Document.

+

This document is governed by the 12 June 2023 W3C Process Document.

@@ -880,7 +880,7 @@

1.2.1. Detect the presence of multiple screens

@@ -910,7 +910,7 @@

1.2.2. Detect Screen attribute changes

Observing legacy Screen attribute changes is useful for adapting content, even on single-screen devices. Furthermore, observing isExtended is useful for detecting transitions between single-screen and multi-screen configurations. To avoid polling, change events are fired at the Screen object:

screen.addEventListener('change', e => {
-  // An attribute of the legacy `Screen` interface has changed.
+  // An attribute of the legacy \`Screen\` interface has changed.
 });

1.2.3. Request detailed screen information

@@ -944,7 +944,7 @@

1.2.4. Place fullscreen content on a specific screen

A common multi-screen use case is to present some content fullscreen on a specific screen. The screen may be selected interactively, or automatically selected based on screen attributes or prior user selections. A screen, once selected, can be passed to the requestFullscreen() method.

-
// Call an assumed helper that returns a selected `ScreenDetailed` instance.
+
// Call an assumed helper that returns a selected \`ScreenDetailed\` instance.
 const screenDetailed = getScreenForSlideshow();
 
 // Request that a particular element be shown fullscreen on the selected screen.
@@ -958,8 +958,8 @@ 
1.2.6. Initiate multi-screen experiences

    
A commonly requested multi-screen use case is to initiate a compelling multi-screen experience from a single user activation. One specific proposed form is permitting a site to § 1.2.4 Place fullscreen content on a specific screen and § 1.2.5 Place windows on a specific screen from a single user gesture. This can be accomplished by first requesting fullscreen on a specific screen of a multi-screen device, and then opening a popup window on another screen of the device, in a single event listener.

@@ -970,11 +970,11 @@ 
2. Concepts

    
Concepts in this specification build upon those in the CSSOM-View-1 Working Draft, and the CSSOM-View-1 Editor’s Draft, [HTML], and [Fullscreen].