Skip to content

Add a note about limiting the image density srcset takes into account - #5901

Open
yoavweiss wants to merge 2 commits into
whatwg:mainfrom
yoavweiss:srcset_cap_note
Open

Add a note about limiting the image density srcset takes into account#5901
yoavweiss wants to merge 2 commits into
whatwg:mainfrom
yoavweiss:srcset_cap_note

Conversation

@yoavweiss

@yoavweiss yoavweiss commented Sep 9, 2020 •
edited by pr-preview Bot
Loading

Copy link
Copy Markdown
Contributor

Closes #4421

Chrome plans to experiment with limiting the density value that srcset takes into account when selecting sources.
As the image source selection algorithm is UA-specific, other implementer may or may not try to follow, but I thought that adding a note to that effect can help.

The change is not WPT testable as:
a) It's a note.
b) It refers to user-agent specific selection

If needed, I'm happy to file relevant implementation bugs.

(See WHATWG Working Mode: Changes for more details.)

💥 Error: Wattsi server error 💥

PR Preview failed to build. (Last tried on Jan 15, 2021, 8:00 AM UTC).

More

PR Preview relies on a number of web services to run. There seems to be an issue with the following one:

🚨 Wattsi Server - Wattsi Server is the web service used to build the WHATWG HTML spec.

🔗 Related URL

<html>
<head><title>504 Gateway Time-out</title></head>
<body bgcolor="white">
<center><h1>504 Gateway Time-out</h1></center>
<hr><center>nginx/1.10.3</center>
</body>
</html>

If you don't have enough information above to solve the error by yourself (or to understand to which web service the error is related to, if any), please file an issue.

@yoavweiss

yoavweiss commented Sep 9, 2020

Copy link
Copy Markdown
Contributor Author

@eeeps - can you take a look to see if I reached the right conclusions from your research?

@yoavweiss

yoavweiss commented Sep 9, 2020

Copy link
Copy Markdown
Contributor Author

@zcorpan @annevk - care to take a look?

@1jj

1jj commented Sep 10, 2020

Copy link
Copy Markdown

Research suggests that the human ability to see differences between high-density images and lower-density ones diminishes as screen and image density increases, and the differences become indistinguishable with image densities between 2.0 and 2.2.

What I see in the image below is:
For a vast majority of persons the differences become indistinguishable with image densities larger than 2.

2.2 is apparent precision only and not really helpful.

annevk
annevk reviewed Sep 11, 2020
View reviewed changes
Comment thread source
</ol>

<p class="note"><a
href="https://observablehq.com/@eeeps/visual-acuity-and-device-pixel-ratio">Research</a>

@annevk annevk Sep 11, 2020

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This should be in the reference section. Also not sure we should call it research unless it's a peer-reviewed paper?

Base automatically changed from master to main January 15, 2021 07:58
@austinh austinh mentioned this pull request Oct 13, 2026
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@annevk annevk annevk left review comments

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

topic: img

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Responsive images causes performance issues on high-resolution devices

3 participants

@yoavweiss @1jj @annevk