Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

feat: Add splashscreens member + purpose (closes #510) #530

Closed
wants to merge 2 commits into from
Closed

feat: Add splashscreens member + purpose (closes #510) #530

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c332028
feat: Add splashscreens member + purpose (closes #510)
marcoscaceres Nov 18, 2016
2719b69
editorial: use @stevefaulkner's a11y suggestion
marcoscaceres Nov 28, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
69 changes: 59 additions & 10 deletions index.html
View file
Open in desktop
Expand Up @@ -1272,6 +1272,11 @@ <h3>
<var>manifest</var>, <var>manifest URL</var>, and "icons" as
arguments.
</li>
<li>Let <var>splashscreens</var> of <var>parsed manifest</var> be the
result of running the <a>steps for processing an array of images</a>
with <var>manifest</var>, <var>manifest URL</var>, and
"splashscreens" as arguments.
</li>
<li>Let <var>scope</var> of <var>parsed manifest</var> be the result
of running the <a>steps for processing the <code>scope</code>
member</a> with <var>manifest</var>, <var>manifest URL</var>,
Expand Down Expand Up @@ -1747,16 +1752,6 @@ <h3>
The <code>icons</code> member is processed using the <a>steps for
processing an array of images</a>.
</p>
<p>
If there are multiple equally appropriate icons in <var>icons</var>,
a user agent MUST use the last one declared in order at the time that
the user agent collected the list of <var>icons</var>. If the user
agent tries to use an icon but that icon is determined, upon closer
examination, to in fact be inappropriate (e.g. because its content
type is unsupported), then the user agent MUST try the
next-most-appropriate icon as determined by examining the <a>image
object's</a> members.
</p>
<div class="example">
<p>
In the following example, the developer has made the following
Expand Down Expand Up @@ -1930,6 +1925,43 @@ <h3>
</li>
</ol>
</section>
<section>
<h3>
<code>splashscreens</code> member
</h3>
<p>
A <dfn>splash screen</dfn> is a graphical representation (usually an
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should this read splashscreens instead of splash screen?

the other member sections start like this. is that an issue

image on a background color) that is presented as the end user before
the user agent is able render content. A splash screen is intended to
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

a few typos caught:

  • presented as the end user -> presented to the end user
  • is able render → is able to render

convey to the end-user that the web application is being prepared for
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

end-user is end user above. can you choose the same one to be consistent?

them in the background.
</p>
<p>
When showing a <a>splash screen</a>, a user agent MUST expose the
loading state of the application via the platform's accessibility
API(s).
</p>
<p>
The <dfn id="member-splashscreens"><code>splashscreens</code>
member</dfn> is an <a>array</a> of <a>image objects</a> that can
serve as the splash screen for a web application.
</p>
<pre class="example">
{
"splashscreens": [{
"src": "icon/lowres.webp",
"sizes": "148x148",
"type": "image/webp"
}, {
"src": "icon/lowres",
"sizes": "248x248"
}, {
"src": "icon/hd_hi.svg",
"sizes": "1000x1000"
}]
}
</pre>
</section>
<section>
<h3>
<code>start_url</code> member
Expand Down Expand Up @@ -2315,6 +2347,16 @@ <h2>
scenarios to avoid losing important information through, e.g., change
of color or clipped corners.
</p>
<p>
Where there are multiple equally appropriate <a>image objects</a> for a
particular <a>purpose</a> or manifest member, a user agent MUST use the
last one declared in order at the time that the user agent collected
the list of image objects. If the user agent tries to use an image
object but that image is determined, upon closer examination, to in
fact be inappropriate (e.g. because its content type is unsupported),
then the user agent MUST try the next-most-appropriate image as
determined by examining the <a>image object's</a> members.
</p>
<section>
<h3>
Fetching image objects
Expand Down Expand Up @@ -2439,6 +2481,13 @@ <h3>
A user agent can present this icon where space constraints and/or
color requirements differ from those of the application icon.
</dd>
<dt>
<dfn data-lt="splashscreen purpose">splashscreen</dfn>:
</dt>
<dd>
A user agent can present this icon where it would present a
<a>splash screen</a>.
</dd>
<dt>
<dfn data-lt="any purpose">any</dfn>:
</dt>
Expand Down