- From: grigs via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 Mar 2023 19:12:51 +0000
- To: public-css-archive@w3.org
> @grigs For new image formats, as far as I can tell the art direction use case is not handled. With the bookstore demo also it's a completely different image, not just a crop. I suppose an image file could in theory contain different images though. Not that it matters for your greater point, but the bookstore demo is the same image with CSS effects applied to it in different contexts. `<picture>` likely requires some form of mapping the queries on the sources inside the container to the size of the container and the something on the container itself to the viewport. So the art direction use case would still require `<picture>` and `<source>` options, but progressive downloading of an image could remove the need for `sizes` and multiple options in the `srcset`. It seems that developers have had the most trouble using `sizes` and `srcset` correctly. And unlike the problems with developers setting `sizes` values incorrectly, when I see `<picture>` misused, it is usually scenarios where `sizes` and `srcset` should be used instead. Web Almanac says [`<picture>` is used 7.7% of the time](https://almanac.httparchive.org/en/2022/media#picture). So if we can simplify the resolution switching use case, we’re going to simplify over 90% of responsive images. -- GitHub Notification of comment by grigs Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5889#issuecomment-1460719965 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 8 March 2023 19:12:53 UTC