Skip to content

Commit

Permalink
Ran tidy. #chore (#94)
Browse files Browse the repository at this point in the history 
A lot of changes had landed without a tidy, making it very difficult to
do any more work on the document.
  • Loading branch information
@mgiuca
mgiuca authored Mar 27, 2024
1 parent 490f4af commit a6ffc2b
Showing 1 changed file with 89 additions and 93 deletions.
182 changes: 89 additions & 93 deletions index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -48,28 +48,27 @@
</section>
<section>
<h2>
<code>
<dfn data-export="" data-dfn-for="manifest">display_override</dfn>
</code> member
<code><dfn data-export="" data-dfn-for=
"manifest">display_override</dfn></code> member
</h2>
<p>
For advanced usages, the [=manifest/display_override=] member can be
used to specify a custom fallback order of <a data-cite=
"appmanifest#dfn-display-modes-list">display mode list values</a> for
developers to choose their preferred <a data-cite=
"appmanifest#dfn-display">display mode</a> for the web application.
Its value is a [=display mode=].
"appmanifest#dfn-display">display mode</a> for the web application. Its
value is a [=display mode=].
</p>
<p>
The [=manifest/display_override=] member of the [=application manifest=]
is a <a>sequence</a> of <a data-cite=
The [=manifest/display_override=] member of the [=application
manifest=] is a <a>sequence</a> of <a data-cite=
"appmanifest#dfn-display-modes-list">display mode list values</a>
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 <a data-cite=
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 <a data-cite=
"appmanifest#dfn-process-the-display-member">processing the display
members</a> for the algorithm steps.
</p>
Expand All @@ -84,13 +83,12 @@ <h2>
|manifest:ordered map|.[=manifest/display_override=] member:
<ol class="algorithm">
<li>If <a data-cite="appmanifest/#dfn-display-modes-list">display
modes list</a> contains |candidate_display_mode:DisplayModeType|,
return that |candidate_display_mode:DisplayModeType|
modes list</a> contains |candidate_display_mode:DisplayModeType|,
return that |candidate_display_mode:DisplayModeType|
</li>
<li>If |candidate_display_mode:DisplayModeType| is
[=display mode/window-controls-overlay=] and the user agent
supports this, then return that
|candidate_display_mode:DisplayModeType|.
<li>If |candidate_display_mode:DisplayModeType| is [=display
mode/window-controls-overlay=] and the user agent supports this,
then return that |candidate_display_mode:DisplayModeType|.
</li>
</ol>
</li>
Expand All @@ -101,59 +99,56 @@ <h2>
display modes. Otherwise, the [=manifest/display=] member is sufficient
for most use cases.
</p>

<section>
<h3>Concepts</h3>
<h3>
Concepts
</h3>
<ul>
<li>
<dfn data-lt="controls of the window">Window controls</dfn>:
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.
</li>
<li>
<dfn>Additional Window Controls</dfn>: feature to replace
[=window controls=] by calling the minimize/maximize/close etc APIs
directly without the need to use browser's native window controls.
<dfn>Additional Window Controls</dfn>: feature to replace [=window
controls=] by calling the minimize/maximize/close etc APIs directly
without the need to use browser's native window controls.
</li>
<li>
<dfn data-lt="IWA">Isolated Web App</dfn>: 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 <a href="https://github.com/WICG/isolated-web-apps">explainer</a>.
can be used offline instead of being fetched over HTTPS. See
<a href="https://github.com/WICG/isolated-web-apps">explainer</a>.
</li>
</ul>
</section>

<section>
<h3>
Display mode extensions
</h3>
<p>
Additionally to the normal
<a data-cite="appmanifest#dfn-display-modes-list">display modes</a>,
Additionally to the normal <a data-cite=
"appmanifest#dfn-display-modes-list">display modes</a>,
[=manifest/display_override=] also supports certain extensions to it.
</p>

<dt>
<dfn data-export="" data-dfn-for="display mode">
borderless
</dfn>
</dt>
<dd>
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.
</dd>

<dt>
[=display mode/window-controls-overlay=]
</dt>

<dl>
<dt>
<dfn data-export="" data-dfn-for="display mode">borderless</dfn>
</dt>
<dd>
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.
</dd>
<dt>
[=display mode/window-controls-overlay=]
</dt>
</dl>
<section class="informative">
<h4>
[=manifest/display_override=] usage example
Expand Down Expand Up @@ -186,31 +181,27 @@ <h4>
<section>
<h3>
Defining <dfn data-export="" data-lt="draggable region">draggable
regions</dfn>
regions</dfn>
</h3>
<p class="issue" title="At risk feature">
[=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 <dfn data-export=""
data-lt="-webkit-app-region">`-webkit-app-region`</dfn> for the same
purpose.
</p>
<p>
The <dfn data-export="" data-lt="app-region">`app-region` </dfn>
property can be used to define with CSS which regions or elements in
for example a title bar are draggable.
</p>
<ul>
<li>
To enable dragging an element, shall be set to `drag`.
</li>
<li>
To disable dragging an element, shall be set to `no-drag`.
</li>
</ul>
<p class="issue" title="At risk feature">
[=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 <dfn data-export="" data-lt=
"-webkit-app-region">`-webkit-app-region`</dfn> for the same purpose.
</p>
<p>
The <dfn data-export="" data-lt="app-region">`app-region`</dfn>
property can be used to define with CSS which regions or elements in
for example a title bar are draggable.
</p>
<ul>
<li>To enable dragging an element, shall be set to `drag`.
</li>
<li>To disable dragging an element, shall be set to `no-drag`.
</li>
</ul>
</section>
</section>

<section>
<h2>
`share_target` member
Expand Down Expand Up @@ -939,34 +930,38 @@ <h2>
<ol>
<li>[=list/for each=] |file| of |files|
<ol>

<li>Let |params:LaunchParams| be a new
<a href="https://wicg.github.io/web-app-launch/#dom-launchparams">
LaunchParams</a> with
<a href="https://wicg.github.io/web-app-launch/#dom-launchparams-files">
files</a> set to a {{FrozenArray}} with a single element
that is a {{FileSystemHandle}} corresponding to |file|.
<li>Let |params:LaunchParams| be a new <a href=
"https://wicg.github.io/web-app-launch/#dom-launchparams">
LaunchParams</a> with <a href=
"https://wicg.github.io/web-app-launch/#dom-launchparams-files">
files</a> set to a {{FrozenArray}} with a single
element that is a {{FileSystemHandle}} corresponding to
|file|.
</li>
<li><a href="https://wicg.github.io/web-app-launch/#dfn-launching-a-web-application-with-handling">
Launch a web application with handling</a> passing
|manifest| and |params|.
<li>
<a href=
"https://wicg.github.io/web-app-launch/#dfn-launching-a-web-application-with-handling">
Launch a web application with handling</a> passing
|manifest| and |params|.
</li>
</ol>
</li>
</ol>
</li>
<li>Else,
<ol>
<li>Let |params:LaunchParams| be a new
<a href="https://wicg.github.io/web-app-launch/#dom-launchparams">
LaunchParams</a> with
<a href="https://wicg.github.io/web-app-launch/#dom-launchparams-files">
files</a> set to a {{FrozenArray}} of {{FileSystemHandle}}s
that correspond to the file paths named by |files|.
<li>Let |params:LaunchParams| be a new <a href=
"https://wicg.github.io/web-app-launch/#dom-launchparams">LaunchParams</a>
with <a href=
"https://wicg.github.io/web-app-launch/#dom-launchparams-files">
files</a> set to a {{FrozenArray}} of {{FileSystemHandle}}s
that correspond to the file paths named by |files|.
</li>
<li><a href="https://wicg.github.io/web-app-launch/#dfn-launching-a-web-application-with-handling">
Launch a web application with handling</a> passing |manifest|
and |params|.
<li>
<a href=
"https://wicg.github.io/web-app-launch/#dfn-launching-a-web-application-with-handling">
Launch a web application with handling</a> passing
|manifest| and |params|.
</li>
</ol>
</li>
Expand Down Expand Up @@ -1204,8 +1199,9 @@ <h3 id="installability-signals">
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.
</p>
<p>
Examples of possible <a>installability signals</a> for a web
Expand Down

0 comments on commit a6ffc2b

Please sign in to comment.