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.

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

Remove problematic icon matching algorithm #1120

Merged
merged 9 commits into from
Jun 6, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 5 additions & 11 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -662,16 +662,6 @@ <h3>
an <abbr title="Operating system">OS</abbr>'s task switcher and/or
system preferences.
</p>
<p>
If there are multiple equally appropriate images in
dmurph marked this conversation as resolved.
Show resolved Hide resolved
[=manifest/icons=], a user agent MUST use the last one declared in
order at the time that the user agent collected the list of
[=manifest/icons=]. If the user agent tries to use an icon but that
icon is determined, upon closer examination, to 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 [=manifest image resource=]'s members.
</p>
<aside class="note">
<p>
When [=processing a manifest=], the [=process image resources=]
Expand Down Expand Up @@ -1660,7 +1650,11 @@ <h3>
<dfn data-dfn-for="icon purpose">any</dfn> (default)
</dt>
<dd>
The user agent is free to display the icon in any context.
The user agent is free to display the icon where no [=manifest
image resource/purpose=] is required. For example, a
[=manifest image resource=] with a "any" purpose
wouldn't be used in a context where "[=icon purpose/monochrome=]"
is required.
</dd>
</dl>
<p>
Expand Down
Loading