Re: -webkit-image-set

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
> >  
> >  
> >  
> >  
>  
>  
>   
>  
>  
>  
>  
>  
>