W3C home > Mailing lists > Public > public-web-perf@w3.org > March 2014

Re: {minutes} 2014-04-26 Web Performance Working Group: Resource Priorities, HRT2, Beacon, etc.

From: David Newton <david@davidnewton.ca>
Date: Sun, 30 Mar 2014 20:10:12 -0400
Cc: Philippe Le Hegaret <plh@w3.org>, public-web-perf <public-web-perf@w3.org>
Message-Id: <EDF3EF26-3B59-4F40-A324-F942789B0997@davidnewton.ca>
To: Tobin Titus <tobint@microsoft.com>

On Mar 30, 2014, at 7:21 PM, Tobin Titus <tobint@microsoft.com> wrote:

> Thanks, David.
>  
> From the TPAC notes:
> http://lists.w3.org/Archives/Public/public-web-perf/2013Nov/0091.html
>  
>  
> Under Meeting Summary, agenda item “3. Resource Priorities”:
> “Additionally, there were concerns with postpone. The WG agreed to scope the spec back to lazyload and work from there.”

Thank you, Tobin. I did see that in the summary, but looking at the actual Meeting Minutes, it appears that this was concern with the postpone CSS property, not the attribute:

> Alois: If you have a postpone on the background image, we don't know that the element is visible yet until we do styling.
> 
> Jason: IE doesn't even download the resources from CSS until the formatting is done.
> 
> Jason: I think we should remove the postpone CSS property as the browser will already do this work.
> 
> Anne: In many cases, it’s hard to know when the image will be in the page.
> 
> Jason: Seems like there is agreement that there is a need for lazyload / postpone, but there may be some confusion in the spec.
> 
> Anne: I think I agree with that.
> 
> Jatinder: Looks like we need to remove the CSS property.
> 
> <Alois> preload none on video 
> http://www.w3schools.com/tags/att_video_preload.asp
> 
> Jason: I think we should scope this to lazyload and then consider adding postpone later on in an Level 2 based on feedback.
> 
> Anne: I think we should consider starting with lazyload. For example, the user agent could interpret lazyload to mean postpone based on data.

From what I can tell, there was no such concern with the attribute, and the decision was only about scoping back the CSS property.

Thanks,
Dave
Received on Monday, 31 March 2014 00:10:38 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:38 UTC