- From: Philippe Le Hegaret <plh@w3.org>
- Date: Thu, 21 Jul 2016 08:46:41 -0400
- To: public-web-perf <public-web-perf@w3.org>
Present: Todd, Ilya, Yoav, PLH, Wesley scribe: Ilya agenda: https://lists.w3.org/Archives/Public/public-web-perf/2016Jul/0000.html Resource Timing ai: we need to add a note on the transition request, followup with plh@ re, transition request L1: plh@ updated the note, should be published tomorrow https://www.w3.org/TR/2016/CR-resource-timing-1-20160721/ https://github.com/w3c/resource-timing/issues/62 ai: followup with Anne about why it was restricted for ACAO consensus on the call is that ABNF allows multiple origins and we should make it so (unless there is something we don't know) ai: we need to create the tests for TAO Charter plh: charter has been approved, should be published soon too! \o/ yoav: make an announcement on WICG discourse to transition perf specs ai: igrigorik@ to start thread on WICG ai: plh@ and yoav@ wll transfer repos (plh -> example with redirect https://github.com/w3c/netinfo) sendBeacon whitelist: https://github.com/w3c/beacon/pull/34 igrigorik / todd: this may belong in L2, as in "how we define this on top of fetch" ai: todd will followup on the bug Updated Security & Privacy section: https://github.com/w3c/hr-time/pull/30 merged. Translating timestamps between globals... https://github.com/w3c/hr-time/issues/22#issuecomment-232738476 plh: should "attribute DOMHighResTimeStamp timeOrigin;" be readonly? toddreifsteck: will followup with team on https://github.com/w3c/hr-time/issues/22#issuecomment-232738476 re, readonly: yes https://github.com/w3c/preload/issues/66 Next meeting: Aug 4th?
Received on Thursday, 21 July 2016 12:46:45 UTC