- From: AndresInSpace via GitHub <sysbot+gh@w3.org>
- Date: Sun, 29 Sep 2024 04:44:07 +0000
- To: public-css-archive@w3.org
If this is not in same topic of the thread, I apologize, the topic seems to be for discussing issues between both html and css defining images, and those processes / specs. I believe it's worth mentioning that there is a discussion in HTML wg [#4421](https://github.com/whatwg/html/issues/4421) regarding an issue where at the browser level there is **no optimization happening** for the current selection process of the image src from a provided srcset, which I believe translates to image-set in CSS and seems to go against [CSS spec](https://www.w3.org/TR/css-images-4/#image-set-notation:~:text=Ideally%2C%20images%20should,image%20to%20load.) and [mdn documentation](https://developer.mozilla.org/en-US/docs/Web/CSS/image/image-set#browser_compatibility:~:text=Resolution%20can%20be%20used%20as%20a%20proxy%20for%20filesize%20%E2%80%94%20a%20user%20agent%20on%20a%20slow%20mobile%20connection%20with%20a%20high%2Dresolution%20screen%20may%20prefer%20to%20receive%20lower%2Dresolution%20images%20rather%20than%20waiting%20for%20a%20higher%20resolution%20image%20to%20load) regarding optimization -- GitHub Notification of comment by AndresInSpace Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5173#issuecomment-2381105657 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 29 September 2024 04:44:08 UTC