W3C home > Mailing lists > Public > public-respimg@w3.org > March 2012

RE: -webkit-image-set

From: Adrian Roselli <Roselli@algonquinstudios.com>
Date: Fri, 23 Mar 2012 16:16:43 -0400
Message-ID: <263F624B0C294348B4D301C32CE3434D0ACF2415@Exchange.development.algonquinstudios.com>
To: Kevin Suttle <kevin@kevinsuttle.com>
CC: <public-respimg@w3.org>
I feel that it can benefit users and user agents to know from the markup what options there are, particularly if CSS files don’t load, given that we’re discussing images that are content (as opposed to images used for decoration).

 

From a strictly semantic standpoint, probably not so much.

 

I had seen people tossing around the idea of an <img> tag extended so that older browsers wouldn’t be excluded. At that point, the options would be there for more capable browsers and the CSS would make the decision which to display. In that scenario I don’t think the semantic question is as much of a concern – assuming the extended <img> tag is implemented well.

 

Something tells me I should go catch up at the site, but without these discussions coming into my inbox I forget to check.

 

 

From: Kevin Suttle [mailto:kevin@kevinsuttle.com] 



 

My message was In reply to Dominique's comment about http://trac.webkit.org/changeset/111637:


 

"I don't think that addresses the markup-based use case, but it probably

should inform it."

 

So, I'm asking, does the markup need to know about multiple image sources if the content is the same? There could be some benefit, I'm sure, but from a semantics standpoint, is it redundant and should it be handled purely in CSS? 

 

KS

On Friday, March 23, 2012 at 4:06 PM, Adrian Roselli wrote:

	Apparently all the discussion on this has taken place on the site, so I know I have missed plenty.

	 

	I don’t understand your question below, though. Does what need a markup-based solution? Providing multiple image options to the browser, or providing sizing information to the browser?

	 

	 

	From: Kevin Suttle [mailto:kevin@kevinsuttle.com] 

	 

	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:17:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:06:06 UTC