- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 28 Apr 2021 16:53:41 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-images] image-set() resolution should be applied on-top of, not instead-of the natural image resolution.`, and agreed to the following: * `RESOLVED: image-set should act like sRCset attribute with applying resolution` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: [css-images] image-set() resolution should be applied on-top of, not instead-of the natural image resolution.<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/6241<br> <dael> emilio: Matches existing impl. Basically spec says if you omit image-set resolution then you use natural image resolution<br> <dael> emilio: If you spec image-set resolution it overrides whatever resolution image has<br> <dael> emilio: Allows to figure out if image has native resolution. Not amazing. Chrome and WK apply image resolution and then image-set resolution. Seems reasonable and sensible<br> <dael> emilio: So this should agree with existing impl<br> <dael> TabAtkins: Happy to resolve on agree with existing impl. I'm not sure how this is supposed to work from reading thread. Do not understand multiplying resolution by exif resolution gives you something usable<br> <dael> emilio: It's a cross-origin info leak<br> <dael> TabAtkins: I suspect something more subtile is happening than I understand. Feels rediculous. But we'll figure it out<br> <dael> emilio: If you find out what it is that's great<br> <dael> TabAtkins: I'd like us to match so happy to resolve<br> <dael> TabAtkins: Prop: image-set should act like source-set attribute with applying resolution<br> <TabAtkins> s/source-set/srcset/<br> <dael> Rossen_: Objections?<br> <dael> RESOLVED: image-set should act like sRCset attribute with applying resolution<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6241#issuecomment-828614908 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 28 April 2021 16:53:44 UTC