- From: Ariel <asw3@dsgml.com>
- Date: Fri, 23 Mar 2012 16:11:31 -0400 (EDT)
- To: Kevin Suttle <kevin@kevinsuttle.com>
- cc: Dominique Hazael-Massieux <dom@w3.org>, public-respimg@w3.org
I disagree. The position of the image is presentation, but that actual content - meaning how many pixels are in the image is content. The visual size is presentation, but the actual physical number of pixels is content. There are two issues here: Changing the layout depending on screen size - that belongs in css certainly. But selecting which image, with the only difference being the dpi does not belong in css, that should be supported in html. -Ariel On Fri, 23 Mar 2012, Kevin Suttle wrote: > This is a point I brought up on the site. To re-cap: > > "img is content, so having it in markup makes sense. However, the size > of an img is presentational. By design, this is most likely a problem > that CSS needs to solve." > > I guess the way I see it, if it is the same image content, does it need > a markup-based solution? We're trying to tackle a > performance/presentation issue. Thoughts? > > KS > > > On Friday, March 23, 2012 at 3:56 AM, Dominique Hazael-Massieux wrote: > >> WebKit has just integrated a patch (from Apple) to make it possible to >> provide variants of a CSS image based on the device scale factor: >> http://trac.webkit.org/changeset/111637 >> >> I don't think that addresses the markup-based use case, but it probably >> should inform it. >> >> Dom > >
Received on Friday, 23 March 2012 20:12:01 UTC