.
thanks,
Zhiheng
-Olli
--
View this message in context:
http://old.nabble.com/-WebTiming--HTMLElement-timing-tp27335161p27427432.html
Sent from the w3.org - public-webapps mailing list archive at
Nabble.com.
On Wed, Feb 17, 2010 at 10:36 PM, James Robinson jam...@google.com wrote:
* What precisely does 'parse' time mean for each element? For example, on a
script tag does parse time include parsing the script itself, or executing
it as well? What about for JS engines that do not distinguish
if these pages
are all in a direction chain. From the user's perspective, the waiting
begins with the fetching of the first page in a
redirection chain.
thanks,
Zhiheng
-Olli
--
View this message in context:
http://old.nabble.com/-WebTiming--HTMLElement-timing
.
thanks,
Zhiheng
-Olli
--
View this message in context:
http://old.nabble.com/-WebTiming--HTMLElement-timing-tp27335161p27427432.html
Sent from the w3.org - public-webapps mailing list archive at Nabble.com.
I¹d like to jump in here and address this point:
³While I agree that timing information is important, I don't think it's
going to be so commonly used that we need to add convenience features
for it. Adding a few event listeners at the top of the document does
not seem like a big burden.²
I work
--
View this message in context:
http://old.nabble.com/-WebTiming--HTMLElement-timing-tp27335161p27427432.html
Sent from the w3.org - public-webapps mailing list archive at Nabble.com.
I¹d like to jump in here and address this point:
³While I agree that timing information is important, I don't think it's
going to be so commonly used that we need to add convenience features
for it. Adding a few event listeners at the top of the document does
not seem like a big burden.²
I work
On Mon, Feb 1, 2010 at 5:00 PM, Lenny Rachitsky
lenny.rachit...@webmetrics.com wrote:
I’d like to jump in here and address this point:
“While I agree that timing information is important, I don't think it's
going to be so commonly used that we need to add convenience features
for it. Adding a
Understood. I used to run the engineering department here at Webmetrics so I
understand the cost/benefit decisions that need to be made with any new
functionality. However coming from the web performance industry anything
that could help website owners understand and track their performance better
Hi, James,
Good point indeed. Some evaluation has been done here with camstudio.
Using paint event
helps in many cases but, for the reasons you mentioned, it's not yet
reliable enough. So if it's
worthwhile to do it in this spec is indeed debatable.
A related question and one that many of
Somehow Lenny's comments got lost from the list.
On Tue, Feb 2, 2010 at 10:57 AM, Lenny Rachitsky
lenny.rachit...@webmetrics.com wrote:
I’d like to jump in here and address this point:
“While I agree that timing information is important, I don't think it's
going to be so commonly used
Hi, Olli,
On Fri, Jan 29, 2010 at 6:15 AM, Olli Pettay olli.pet...@helsinki.fiwrote:
On 1/27/10 9:39 AM, Zhiheng Wang 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
Jonas,
On Fri, Jan 29, 2010 at 12:50 AM, Jonas Sicking jo...@sicking.cc wrote:
On Thu, Jan 28, 2010 at 10:53 PM, Zhiheng Wang zhihe...@google.com
wrote:
Also, what is the use case for the Ticks interface?
The Ticks interface is a convenient way to store time measurements
and
On Tue, Feb 2, 2010 at 10:36 AM, Zhiheng Wang zhihe...@google.com wrote:
Hi, Olli,
On Fri, Jan 29, 2010 at 6:15 AM, Olli Pettay olli.pet...@helsinki.fiwrote:
On 1/27/10 9:39 AM, Zhiheng Wang wrote:
Folks,
Thanks to the much feedback from various developers, the WebTiming
specs has
On Thu, Jan 28, 2010 at 10:53 PM, Zhiheng Wang zhihe...@google.com wrote:
Also, what is the use case for the Ticks interface?
The Ticks interface is a convenient way to store time measurements
and
retrieve it later on a page.
I will have some example there.
Why not just do:
On 1/27/10 9:39 AM, Zhiheng Wang 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
On Wed, Jan 27, 2010 at 5:57 PM, Jonas Sicking jo...@sicking.cc wrote:
On Wed, Jan 27, 2010 at 5:30 PM, Zhiheng Wang zhihe...@google.com wrote:
Hi, Jonas,
Thanks for the comments. pls find comments inline.
On Wed, Jan 27, 2010 at 12:12 AM, Jonas Sicking jo...@sicking.cc
wrote:
On
On Tue, Jan 26, 2010 at 11:39 PM, Zhiheng Wang zhihe...@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
Hi, Jonas,
Thanks for the comments. pls find comments inline.
On Wed, Jan 27, 2010 at 12:12 AM, Jonas Sicking jo...@sicking.cc wrote:
On Tue, Jan 26, 2010 at 11:39 PM, Zhiheng Wang zhihe...@google.com
wrote:
Folks,
Thanks to the much feedback from various developers, the WebTiming
On Wed, Jan 27, 2010 at 5:30 PM, Zhiheng Wang zhihe...@google.com wrote:
Hi, Jonas,
Thanks for the comments. pls find comments inline.
On Wed, Jan 27, 2010 at 12:12 AM, Jonas Sicking jo...@sicking.cc wrote:
On Tue, Jan 26, 2010 at 11:39 PM, Zhiheng Wang zhihe...@google.com
wrote:
Folks,
On Wed, Jan 27, 2010 at 5:57 PM, Jonas Sicking jo...@sicking.cc wrote:
On Wed, Jan 27, 2010 at 5:30 PM, Zhiheng Wang zhihe...@google.com wrote:
Hi, Jonas,
Thanks for the comments. pls find comments inline.
On Wed, Jan 27, 2010 at 12:12 AM, Jonas Sicking jo...@sicking.cc wrote:
On Tue, Jan
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/
22 matches
Mail list logo
