Skip to content

Commit

Permalink
chore: remove redundant dependencies (w3c#857)
Browse files Browse the repository at this point in the history
  • Loading branch information
@christianliebel
Marcos Cáceres authored and christianliebel committed May 27, 2020
1 parent 639dca1 commit 0a0372c
Showing 1 changed file with 58 additions and 124 deletions.
182 changes: 58 additions & 124 deletions index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -134,20 +134,20 @@
}
</style>
</head>
<body data-cite="ENCODING">
<body data-cite="ENCODING SCREEN-ORIENTATION">
<section id='abstract'>
<p>
This specification defines a JSON-based manifest file that provides
developers with a centralized place to put metadata associated with a
web application. This metadata includes, but is not limited to, the web
application's name, links to icons, as well as the preferred URL to
open when a user launches the web application. The manifest also allows
developers to declare a default orientation for their web application,
as well as providing the ability to set the display mode for the
application (e.g., in fullscreen). Additionally, the manifest allows a
developer to "scope" a web application to a URL. This restricts the
URLs to which the manifest is applied and provides a means to "deep
link" into a web application from other applications.
developers to declare a default screen orientation for their web
application, as well as providing the ability to set the display mode
for the application (e.g., in fullscreen). Additionally, the manifest
allows a developer to "scope" a web application to a URL. This
restricts the URLs to which the manifest is applied and provides a
means to "deep link" into a web application from other applications.
</p>
<p>
Using this metadata, user agents can provide developers with means to
Expand Down Expand Up @@ -852,7 +852,7 @@ <h2>
navigation scope will be <code>/pages/</code>.
</p>
<p>
Developers should take care, if they rely on the default behaviour,
Developers should take care, if they rely on the default behavior,
that all of the application's page URLs begin with the parent path of
the start URL. To be safe, explicitly specify <a>scope</a>.
</p>
Expand Down Expand Up @@ -1356,9 +1356,10 @@ <h3>
<li>If <var>manifest link</var>'s <code>href</code> attribute's value
is the empty <a>string</a>, then abort these steps.
</li>
<li>Let <var>manifest URL</var> be the result of <a>parsing</a> the
value of the <code>href</code> attribute, relative to <a>the
element's base URL</a>. If parsing fails, then abort these steps.
<li>Let <var>manifest URL</var> be the result of [=URL
Parser|parsing=] the value of the <code>href</code> attribute,
relative to <a>the element's base URL</a>. If parsing fails, then
abort these steps.
</li>
<li>Let |request:Request| be a new <a>Request</a>.
</li>
Expand Down Expand Up @@ -1496,9 +1497,9 @@ <h3>
</li>
</ol>
</li>
<li>Let <var>manifest</var> be the result of <a data-lt=
"to idl dictionary value">converting</a> <var>json</var> to a
<a>WebAppManifest</a> dictionary.
<li>Let <var>manifest</var> be the result of [=converted to an idl
value|converting=] <var>json</var> to a <a>WebAppManifest</a>
dictionary.
</li>
<li>Set <var>manifest</var>["<a>start_url</a>"] to the result of
running <a>processing the <code>start_url</code> member</a> given
Expand Down Expand Up @@ -1584,8 +1585,8 @@ <h3 id="applying">
</div>
<p>
The appropriate time to <a>apply</a> a manifest is when the
<a>application context</a> is created and before <a>navigation</a> to
the <a>start URL</a> begins.
<a>application context</a> is created and before
[=navigate|navigation=] to the <a>start URL</a> begins.
</p>
</section>
<section id="updating">
Expand Down Expand Up @@ -1808,13 +1809,13 @@ <h3>
<a>URL</a>.
</p>
<ol>
<li>Let <var>default</var> be the result of <a>parsing</a> ".", using
<var>start URL</var> as the <var>base</var> URL.
<li>Let <var>default</var> be the result of [=URL Parser|parsing=]
".", using <var>start URL</var> as the <var>base</var> URL.
</li>
<li>If <var>value</var> is the empty <a>string</a>, then return <var>
default</var>.
</li>
<li>Let <var>scope URL</var> be the result of <a>parsing</a>
<li>Let <var>scope URL</var> be the result of [=URL Parser|parsing=]
<var>value</var>, using <var>manifest URL</var> as the
<var>base</var> URL.
</li>
Expand Down Expand Up @@ -1937,18 +1938,19 @@ <h3>
</h3>
<p>
The <dfn>orientation</dfn> member is a <a>string</a> that serves as
the <a>default orientation</a> for all <a>top-level browsing
the <a>default screen orientation</a> for all <a>top-level browsing
contexts</a> of the web application. The possible values are those of
the {{OrientationLockType}} enum defined in [[SCREEN-ORIENTATION]].
</p>
<p>
If the user agent honors the value of the <a>orientation</a> member
as the <a>default orientation</a>, then that serves as the <a>default
orientation</a> for the life of the web application (unless
overridden by some other means at runtime). This means that the user
agent MUST return the orientation to the <a>default orientation</a>
any time the orientation is unlocked [[SCREEN-ORIENTATION]] or the
<a>top-level browsing context</a> is <a>navigated</a>.
as the <a>default screen orientation</a>, then that serves as the
<a>default screen orientation</a> for the life of the web application
(unless overridden by some other means at runtime). This means that
the user agent MUST return the orientation to the <a>default screen
orientation</a> any time the orientation is unlocked
[[SCREEN-ORIENTATION]] or the <a>top-level browsing context</a> is
<a>navigated</a>.
</p>
<p>
Although the specification relies on the [[SCREEN-ORIENTATION]]'s
Expand All @@ -1962,8 +1964,8 @@ <h3>
together</dfn>. Which orientations and display modes cannot be used
together is left to the discretion of implementers. For example, for
some user agents, it might not make sense to change the <a>default
orientation</a> of an application while in <code>browser</code>
<a>display mode</a>.
screen orientation</a> of an application while in
<code>browser</code> <a>display mode</a>.
</p>
<p class="note">
Once the web application is running, other means can change the
Expand Down Expand Up @@ -2000,7 +2002,7 @@ <h3>
<li>If <var>value</var> is the empty <a>string</a>, return
<var>document URL</var>.
</li>
<li>Let <var>start URL</var> be the result of <a>parsing</a>
<li>Let <var>start URL</var> be the result of [=URL Parser|parsing=]
<var>value</var>, using <var>manifest URL</var> as the
<var>base</var> URL.
</li>
Expand Down Expand Up @@ -2033,7 +2035,7 @@ <h3>
For example, if the value of <a>start_url</a> is
<samp>../start_point.html</samp>, and the manifest's URL is
<samp>https://example.com/resources/manifest.webmanifest</samp>,
then the result of <a>URL parsing</a> would be
then the result of [=URL parser|parsing=] would be
<samp>https://example.com/start_point.html</samp>.
</p>
</div>
Expand Down Expand Up @@ -2368,20 +2370,21 @@ <h3>
<ol>
<li>If <var>shortcut</var>["name"] or <var>shortcut</var>["url"]
are undefined, or if <var>shortcut</var>["name"] is the empty
string, <a>issue a developer warning</a> and <a>continue</a>.
string, <a>issue a developer warning</a> and
[=iteration/continue=].
</li>
<li>Set <var>shortcut</var>["icons"] to the result of running <a>
processing `ImageResource` members</a> given
<var>shortcut</var>["icons"] and <var>manifest URL</var>.
</li>
<li>Set <var>shortcut</var>["url"] to the result of
<a>parsing</a> <var>shortcut</var>["url"] using <var>manifest
<li>Set <var>shortcut</var>["url"] to the result of [=URL
Parser|parsing=] <var>shortcut</var>["url"] using <var>manifest
URL</var> as the base URL. If the result is failure, <a>issue a
developer warning</a> and <a>continue</a>.
developer warning</a> and [=iteration/continue=].
</li>
<li>If <var>shortcut</var>["url"] is not <a>within scope</a> of
<var>manifest URL</var>, <a>issue a developer warning</a> and <a>
continue</a>.
<var>manifest URL</var>, <a>issue a developer warning</a> and
[=iteration/continue=].
</li>
<li>
<a>Append</a> <var>shortcut</var> to
Expand Down Expand Up @@ -2657,8 +2660,8 @@ <h3>
<li>Set |canonicalKeyword| to <a>ascii lowercased</a> |keyword|.
</li>
<li>If |canonicalKeyword| is not one of the [=icon purposes=], or
|purposes| [=contains=] |keyword|, then [=issue a developer
warning=] and [=iteration/continue=].
|purposes| [=set/contain|contains=] |keyword|, then [=issue a
developer warning=] and [=iteration/continue=].
</li>
<li>Otherwise, [=set/append=] |canonicalKeyword| to |purposes|.
</li>
Expand Down Expand Up @@ -2837,15 +2840,15 @@ <h3>
consisting of an <a>unordered set of unique space-separated
tokens</a> which are <a>ASCII case-insensitive</a> that represents
the dimensions of an image. Each keyword is either an <a>ASCII
case-insensitive</a> match for the <a>string</a> "<a data-lt=
"any link size">any"</a>, or a value that consists of two <a>valid
non-negative integers</a> that do not have a leading U+0030 DIGIT
ZERO (0) character and that are separated by a single U+0078 LATIN
SMALL LETTER X or U+0058 LATIN CAPITAL LETTER X character. The
keywords represent icon sizes in raw pixels (as opposed to CSS
pixels). When multiple <a>ImageResource</a>s are available, a user
agent MAY use the value to decide which icon is most suitable for a
display context (and ignore any that are inappropriate).
case-insensitive</a> match for the <a>string</a> "any", or a value
that consists of two <a>valid non-negative integers</a> that do not
have a leading U+0030 DIGIT ZERO (0) character and that are separated
by a single U+0078 LATIN SMALL LETTER X or U+0058 LATIN CAPITAL
LETTER X character. The keywords represent icon sizes in raw pixels
(as opposed to CSS pixels). When multiple <a>ImageResource</a>s are
available, a user agent MAY use the value to decide which icon is
most suitable for a display context (and ignore any that are
inappropriate).
</p>
<p>
The steps for <dfn>processing the <code>sizes</code> member of an
Expand Down Expand Up @@ -2950,8 +2953,8 @@ <h3>
<li>Let <var>image</var> be a new object created as if by the
expression ({}).
</li>
<li>Set <var>image</var>["src"] to the result of
<a>parsing</a> <var>entry</var>["src"] using <var>manifest
<li>Set <var>image</var>["src"] to the result of [=URL
Parser|parsing=] <var>entry</var>["src"] using <var>manifest
URL</var> as the base URL.
</li>
<li>Set <var>image</var>["type"] to the result of running <a>
Expand Down Expand Up @@ -3232,9 +3235,9 @@ <h3>
<li>If <var>application URL</var> is <code>undefined</code>, return
<code>undefined</code>.
</li>
<li>Otherwise, <a>parse</a> <var>application URL</var> and if the
result is not failure, return the result, otherwise return
<code>undefined</code>.
<li>Otherwise, [=URL Parser|parse=] <var>application URL</var> and if
the result is not failure, return the result, otherwise return <code>
undefined</code>.
</li>
</ol>
</section>
Expand Down Expand Up @@ -3761,10 +3764,10 @@ <h2>
<section id="idl-index" class="appendix">
<!-- All the Web IDL will magically appear here -->
</section>
<section class="appendix">
<h3>
<section id="index" class="appendix">
<h2>
Terms defined by reference
</h3>
</h2>
<p>
As the manifest uses the JSON format, this specification relies on the
types defined in [[ECMA-404]] specification: namely <dfn>object</dfn>,
Expand All @@ -3776,27 +3779,6 @@ <h3>
expected.
</p>
<ul class="index" data-sort="">
<li>[[URL]] defines the following terms:
<ul>
<li>
<dfn data-cite="URL#concept-url-parser" data-lt=
"parse|parsing|URL parsing">URL parser</dfn>
</li>
</ul>
</li>
<li>[[SCREEN-ORIENTATION]] defines the following terms:
<ul>
<li>
<dfn data-cite=
"SCREEN-ORIENTATION#dfn-default-orientation">default
orientation</dfn>
</li>
<li>
<dfn data-cite=
"SCREEN-ORIENTATION#dom-orientationlocktype">OrientationLockType</dfn>
</li>
</ul>
</li>
<li>[[CSS-SYNTAX-3]] defines the following terms:
<ul>
<li>
Expand All @@ -3805,27 +3787,6 @@ <h3>
</li>
</ul>
</li>
<li>[[CSP3]] defines the following terms:
<ul>
<li>
<a data-cite=
"CSP3#directive-manifest-src"><dfn>manifest-src</dfn>
directive</a>
</li>
<li>
<a data-cite="CSP3#directive-default-src"><dfn>default-src</dfn>
directive</a>
</li>
</ul>
</li>
<li>[[SECURE-CONTEXTS]] defines the following terms:
<ul>
<li>
<a data-cite="SECURE-CONTEXTS#is-origin-trustworthy"><dfn>Is
origin potentially trustworthy</dfn></a>
</li>
</ul>
</li>
<li>[[ECMA-402]] defines the following terms:
<ul>
<li>
Expand All @@ -3838,15 +3799,6 @@ <h3>
</li>
</ul>
</li>
<li>[[WEBIDL]] defines the following terms:
<ul>
<li>
<a data-cite="WEBIDL#es-dictionary"><dfn data-lt=
"to idl dictionary value">converted to IDL dictionary
value</dfn></a>
</li>
</ul>
</li>
<li>[[DOM]] defines the following terms:
<ul>
<li>
Expand All @@ -3870,21 +3822,13 @@ <h3>
"HTML#unordered-set-of-unique-space-separated-tokens"><dfn>unordered
set of unique space-separated tokens</dfn></a>
</li>
<li>
<a data-cite="HTML#navigate"><dfn data-lt=
"navigated|navigate|navigation">navigate algorithm</dfn></a>
</li>
<li>
<a data-cite="HTML#linkTypes"><dfn>link type</dfn></a>
</li>
<li>
<a data-cite="HTML#delay-the-load-event"><dfn>delay the load
event</dfn></a>
</li>
<li>
<a data-cite="HTML#attr-link-sizes-any"><dfn>any link
size</dfn></a>
</li>
<li>
<a data-cite="HTML#valid-non-negative-integer"><dfn>valid
non-negative integer</dfn></a>
Expand All @@ -3903,16 +3847,6 @@ <h3>
</li>
</ul>
</li>
<li>[[INFRA]] defines the following terms:
<ul>
<li>
<dfn data-cite="INFRA#list-contain">contains</dfn>
</li>
<li>
<dfn data-cite="INFRA#iteration-continue">continue</dfn>
</li>
</ul>
</li>
<li>[[ECMASCRIPT]] defines the following terms:
<ul>
<li>
Expand Down

0 comments on commit 0a0372c

Please sign in to comment.