[Webkit-unassigned] [Bug 101017] Web Inspector: Support user timing mark and measure in Timeline panel

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Nov 12 19:19:11 PST 2012


--- Comment #5 from pdeng6 <pan.deng at intel.com>  2012-11-12 19:20:55 PST ---
(In reply to comment #2)
> (In reply to comment #1)
> > Could you explain why we need another method of marking the timeline? Also, note that console.time and timeEnd allows selecting a region on the timeline today.
> I.e. I think they make sense wherever rest of the performance API is visualized. Otherwise it will be hard for the developer to find correlation between these signals and the other ones originating from the inspector instrumentation. Like timeline has been using wall clock until recently.

What if wall clock adjusted during instrumentation?

> Alternatively, we could deprecate console's time methods and make sure performance API is aligned with the inspector data. That might require re-implementing some of performance guts on top of inspector instrumentation. Tony, James, what do you think, could we try aligning them?

Encourage developer to use user timing to mark timeline as standard is reasonable, as standard.
I guess re-implementing performance on top of inspector instrumentation is not a must if timing mechanism is aligned.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list