From a6ffc2b10d0a586e1fb02b4422bb8ec0ae488697 Mon Sep 17 00:00:00 2001 From: Matt Giuca Date: Wed, 27 Mar 2024 16:10:06 +1100 Subject: [PATCH] Ran tidy. #chore (#94) A lot of changes had landed without a tidy, making it very difficult to do any more work on the document. --- index.html | 182 ++++++++++++++++++++++++++--------------------------- 1 file changed, 89 insertions(+), 93 deletions(-) diff --git a/index.html b/index.html index aafc46c..5c909a5 100644 --- a/index.html +++ b/index.html @@ -48,28 +48,27 @@

- - display_override - member + display_override member

For advanced usages, the [=manifest/display_override=] member can be used to specify a custom fallback order of display mode list values for developers to choose their preferred display mode for the web application. - Its value is a [=display mode=]. + "appmanifest#dfn-display">display mode for the web application. Its + value is a [=display mode=].

- The [=manifest/display_override=] member of the [=application manifest=] - is a sequence of sequence of display mode list values including extensions like [=display mode/window-controls-overlay=] and [=display mode/borderless=]. This member represents the developer's - preferred fallback chain for [=display mode=]s. This field overrides the - [=manifest/display=] member. If the user agent does not support any of - the [=display mode=]s specified here, then it falls back to considering - the [=manifest/display=] member. See processing the display members for the algorithm steps.

@@ -84,13 +83,12 @@

|manifest:ordered map|.[=manifest/display_override=] member:
  1. If display - modes list contains |candidate_display_mode:DisplayModeType|, - return that |candidate_display_mode:DisplayModeType| + modes list contains |candidate_display_mode:DisplayModeType|, + return that |candidate_display_mode:DisplayModeType|
    2. -
  2. If |candidate_display_mode:DisplayModeType| is - [=display mode/window-controls-overlay=] and the user agent - supports this, then return that - |candidate_display_mode:DisplayModeType|. +
  3. If |candidate_display_mode:DisplayModeType| is [=display + mode/window-controls-overlay=] and the user agent supports this, + then return that |candidate_display_mode:DisplayModeType|.
@@ -101,59 +99,56 @@

display modes. Otherwise, the [=manifest/display=] member is sufficient for most use cases.

-
-

Concepts

+

+ Concepts +

  • Window controls: - interface elements that the operating system uses consistently across - applications to enable the user to perform certain actions to control - the application. Common actions in the [=window controls=] include - minimize, maximize/restore, and close buttons. + interface elements that the operating system uses consistently + across applications to enable the user to perform certain actions + to control the application. Common actions in the [=window + controls=] include minimize, maximize/restore, and close buttons.
  • - Additional Window Controls: feature to replace - [=window controls=] by calling the minimize/maximize/close etc APIs - directly without the need to use browser's native window controls. + Additional Window Controls: feature to replace [=window + controls=] by calling the minimize/maximize/close etc APIs directly + without the need to use browser's native window controls.
  • Isolated Web App: feature for installed and signed web applications which are packaged as Web Bundles and - can be used offline instead of being fetched over HTTPS. - See explainer. + can be used offline instead of being fetched over HTTPS. See + explainer.
-

Display mode extensions

- Additionally to the normal - display modes, + Additionally to the normal display modes, [=manifest/display_override=] also supports certain extensions to it.

- -
- - borderless - -
-
- The web application does not have any host-native title bar or - [=window controls=] visible and with the web contents extended to the - whole title bar area. The app can specify [=draggable region=]s in the - web contents to create a customized title bar. The user agent may - change the title bar state depending on various security - considerations, like an out-of-scope navigation. -
- -
- [=display mode/window-controls-overlay=] -
- +
+
+ borderless +
+
+ The web application does not have any host-native title bar or + [=window controls=] visible and with the web contents extended to + the whole title bar area. The app can specify [=draggable region=]s + in the web contents to create a customized title bar. The user + agent may change the title bar state depending on various security + considerations, like an out-of-scope navigation. +
+
+ [=display mode/window-controls-overlay=] +
+

[=manifest/display_override=] usage example @@ -186,31 +181,27 @@

Defining draggable - regions + regions

-

- [=app-region=] CSS property has not been implemented in any user - agent, so it is at risk. Note that some user agents use the - non-standard CSS property `-webkit-app-region` for the same - purpose. -

-

- The `app-region` - property can be used to define with CSS which regions or elements in - for example a title bar are draggable. -

-
    -
  • - To enable dragging an element, shall be set to `drag`. -
    • -
  • - To disable dragging an element, shall be set to `no-drag`. -
    • -
+

+ [=app-region=] CSS property has not been implemented in any user + agent, so it is at risk. Note that some user agents use the + non-standard CSS property `-webkit-app-region` for the same purpose. +

+

+ The `app-region` + property can be used to define with CSS which regions or elements in + for example a title bar are draggable. +

+
    +
  • To enable dragging an element, shall be set to `drag`. +
    • +
  • To disable dragging an element, shall be set to `no-drag`. +
    • +

-

`share_target` member @@ -939,17 +930,19 @@

  1. [=list/for each=] |file| of |files|
      - -
    1. Let |params:LaunchParams| be a new - - LaunchParams with - - files set to a {{FrozenArray}} with a single element - that is a {{FileSystemHandle}} corresponding to |file|. +
    2. Let |params:LaunchParams| be a new + LaunchParams with + files set to a {{FrozenArray}} with a single + element that is a {{FileSystemHandle}} corresponding to + |file|.
      3. -
    3. - Launch a web application with handling passing - |manifest| and |params|. +
    4. + + Launch a web application with handling passing + |manifest| and |params|.
    2. @@ -957,16 +950,18 @@

  2. Else,
      -
    1. Let |params:LaunchParams| be a new - - LaunchParams with - - files set to a {{FrozenArray}} of {{FileSystemHandle}}s - that correspond to the file paths named by |files|. +
    2. Let |params:LaunchParams| be a new LaunchParams + with + files set to a {{FrozenArray}} of {{FileSystemHandle}}s + that correspond to the file paths named by |files|.
      3. -
    3. - Launch a web application with handling passing |manifest| - and |params|. +
    4. + + Launch a web application with handling passing + |manifest| and |params|.
    3. @@ -1204,8 +1199,9 @@

    user agent that a web application can be installed. These signals will vary per user agent, as each user agent will have its own heuristics to determine whether a web site is elegible of an install - prompt. Implementers generally will provide documentation that describe their particular installabilty signals - or other relevant criteria a web application needs to meet to be deemed installable. + prompt. Implementers generally will provide documentation that + describe their particular installabilty signals or other relevant + criteria a web application needs to meet to be deemed installable.

    Examples of possible installability signals for a web