W3C home > Mailing lists > Public > public-respimg@w3.org > July 2013

Re: Meet-up with browser representatives and the W3C

From: Marcos Caceres <w3c@marcosc.com>
Date: Sun, 28 Jul 2013 15:58:50 +0100
Message-ID: <CAAwChxNGjahd=Zj0C4wWhWzKfVSTJceo6n0DV5uaMzBtVFdLvw@mail.gmail.com>
To: Matthieu Larcher <mlarcher@ringabell.org>
Cc: "matmarquis.com" <mat@matmarquis.com>, "public-respimg@w3.org" <public-respimg@w3.org>
On Friday, July 26, 2013, Matthieu Larcher wrote:

> Hi,
>
> Is this event restricted to the main actors and contributors or are simple
> web developers welcome to discuss the matter too ?


 Everyone is welcome, though space is limited. If you would like to attend
just let know soon.


> ML
>
> Le 26/07/2013 19:44, matmarquis.com a écrit :
>
>> All,
>>
>> We’re organizing a meet-up with Mozilla, the W3C, and as many browser
>> representatives as we can gather so that we can discuss a way forward for
>> responsive images. We’re hoping that meeting can take place on the 10th of
>> September in Paris at the Mozilla offices (just before the CSS WG meeting,
>> which starts on the 11th). So far we have confirmations from Apple, Adobe,
>> Google, and Opera.
>>
>> The purpose of the meet-up is to discuss the current proposals
>> ([1],[2],[3]), assess the obstacles to their implementations, and build
>> some momentum. A little more detail:
>>
>> For the last couple of years, various folks—present company in
>> particular—have been working towards finding a way to bring responsive
>> images to the web. Although we now have three proposals on the table
>> (srcset [1], <picture> [2] and client hints [3]), we've had trouble getting
>> sufficient momentum behind browser implementations that would let the
>> market decide which solutions fulfills the use cases most effectively.
>>
>> In the meantime, web developers have had to make do with custom
>> pollyfills which often prevent browsers from loading the image resources
>> until after the DOM was (at least partially) loaded and Javascript on the
>> page has run. This directly hinders the performance work browser engineers
>> have done over the years to optimize resource loading, and get requests on
>> the wire as soon as possible, according to their priority. This leaves
>> developers either giving up all the benefits of preloading or downloading
>> unnecessary data, slowing down the overall load time and inflating
>> bandwidth costs.
>>
>> Proposed agenda:
>>
>> 1. Introduction to each of the proposed solutions
>> 2. Implementor feedback on the solutions
>> 3. Overlap among solutions
>> 4. Next steps
>>
>> Space is fairly limited, so let me know whether you’ll be able to attend
>> as soon as you can. Thanks!
>>
>> -M
>>
>>
>> [1] http://www.w3.org/html/wg/**drafts/srcset/w3c-srcset/<http://www.w3.org/html/wg/drafts/srcset/w3c-srcset/>
>> [2] http://picture.**responsiveimages.org/<http://picture.responsiveimages.org/>
>> [3] https://github.com/igrigorik/**http-client-hints<https://github.com/igrigorik/http-client-hints>
>>
>>
>
>
>
Received on Sunday, 28 July 2013 14:59:18 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:12:39 UTC