Web Performance Working Group Teleconference

<trackbot> Date: 16 April 2014

Resource Priorities

Tobin: I thought that I addressed the question from Ian already

Ilya: what's the status of the spec?
... two flags postpone and lazyload
... still part of the discussion?

Tobin: obviously lazyload would push the download at the bottom of the queue
... and postpone would downlowd it when it comes into view
... but lots of problem woth postpone
... don't necessarely have the layout information, like width and height
... eg grid of images at the bottom of the page
... so loop of download/decode/format/layout
... so idea is to remove postpone
... in theory I'm not sure how it would be practical

Ilya: are the examples public?

Tobin: no, didn't put anything out but can share some screenshots

Ilya: yes, it would be helpful

Tobin: I'd like to move lazyload as far along as possible
... trying to get consensus for lazyload first
... we could bring postpone later

http://lists.w3.org/Archives/Public/public-web-perf/2013Dec/0061.html

plh: that's the original email from Ian
... he is worried about interaction between lazyload, defer, async, ES6

Tobin: I found the additional attributes, whenNeeded, needs
... and I do think we need to come to some agreements
... how to differentiate them and whether all of them are necessary

plh: whenNeeded would overlap with lazyload

Tobin: you could lazyload that and not execute it ith whenNeeded
... so I can see some use cases for both
... I'll have more feedsback next week
... needs one is about dependencies
... so I don't see conflicts between lazyload, whenNeeded and needs so far

plh: any update to the spec?

Tobin: we still had a few questions about postpone
... the minutes were only mentioning removing from CSS

Resolved: postpone is dropped from Resource Priorities. could be brought back later if needed.

Beacon

http://lists.w3.org/Archives/Public/public-web-perf/2014Mar/0015.html

plh: would be good to make progress on that since Mozilla is waiting...
... let's see if Arvind can make next week to move this forward?

Ilya: there is an effort to implement Beacon in blink

<igrigorik__> Blink Intent to implement: https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/Vdi7F7Mk_rM/gxppKdAnLksJ

plh: another reason to move sooner rather later

Ilya: I'll ping Arvind

AOB

plh: we still have outstanding PR request for resource timing and animation timing.

plh: The call with the Privacy IG around Navigation Error Logging is at 9am pacific 04/24 (Thursday)