Skip to content

Commit 2f54efe

Browse files
Remove problematic icon matching algorithm (#1120)
1 parent bceb2ee commit 2f54efe

File tree

1 file changed

+5
-11
lines changed

1 file changed

+5
-11
lines changed

Diff for: index.html

+5-11
Original file line numberDiff line numberDiff line change
@@ -662,16 +662,6 @@ <h3>
662662
an <abbr title="Operating system">OS</abbr>'s task switcher and/or
663663
system preferences.
664664
</p>
665-
<p>
666-
If there are multiple equally appropriate images in
667-
[=manifest/icons=], a user agent MUST use the last one declared in
668-
order at the time that the user agent collected the list of
669-
[=manifest/icons=]. If the user agent tries to use an icon but that
670-
icon is determined, upon closer examination, to be inappropriate
671-
(e.g. because its content type is unsupported), then the user agent
672-
MUST try the next-most-appropriate icon as determined by examining
673-
the [=manifest image resource=]'s members.
674-
</p>
675665
<aside class="note">
676666
<p>
677667
When [=processing a manifest=], the [=process image resources=]
@@ -1660,7 +1650,11 @@ <h3>
16601650
<dfn data-dfn-for="icon purpose">any</dfn> (default)
16611651
</dt>
16621652
<dd>
1663-
The user agent is free to display the icon in any context.
1653+
The user agent is free to display the icon where no [=manifest
1654+
image resource/purpose=] is required. For example, a
1655+
[=manifest image resource=] with a "any" purpose
1656+
wouldn't be used in a context where "[=icon purpose/monochrome=]"
1657+
is required.
16641658
</dd>
16651659
</dl>
16661660
<p>

0 commit comments

Comments
 (0)