- From: Jonas Sicking <jonas@sicking.cc>
- Date: Wed, 27 Jan 2010 18:01:50 -0800
- To: Zhiheng Wang <zhihengw@google.com>
- Cc: public-webapps@w3.org
On Wed, Jan 27, 2010 at 5:57 PM, Jonas Sicking <jonas@sicking.cc> wrote: > On Wed, Jan 27, 2010 at 5:30 PM, Zhiheng Wang <zhihengw@google.com> wrote: >> Hi, Jonas, >> Thanks for the comments. pls find comments inline. >> On Wed, Jan 27, 2010 at 12:12 AM, Jonas Sicking <jonas@sicking.cc> wrote: >>> >>> On Tue, Jan 26, 2010 at 11:39 PM, Zhiheng Wang <zhihengw@google.com> >>> wrote: >>> > Folks, >>> > Thanks to the much feedback from various developers, the WebTiming >>> > specs has undergone some >>> > major revision. Timing info has now been extended to page elements and a >>> > couple more interesting timing >>> > data points are added. The draft is up >>> > on http://dev.w3.org/2006/webapi/WebTiming/ >>> > Feedback and comments are highly appreciated. >>> >>> I take it the idea is that you can get when we for an <img> element >>> start fetching the image, when image data starts arriving etc. I'd >>> prefer if the spec had a comprehensive list of elements that this is >>> expected to be implemented on. >> >> Right now only embedded content elements require these info. An explicit >> list >> might be better though, e.g., <script> is not classified as embedded >> content. > > What do these properties measure on a <figure>? And why would you care > to measure downloading performance on <link rel=icon>? And why > wouldn't you care about <script>? That one seems more performance > critical than any other external resource. Sorry, my bad, it doesn't look like <link> is in this list. This still raises the question why this is specified for <figure>, <embed> and <canvas>, but not for <script> and <link rel=stylesheet>. I also wonder what these properties measure on <svg>? / Jonas
Received on Thursday, 28 January 2010 02:02:43 UTC