Bug 152417 - Web Inspector: Implement console.timeline() and console.timelineEnd()
Summary: Web Inspector: Implement console.timeline() and console.timelineEnd()
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (show other bugs)
Version: WebKit Local Build
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2015-12-17 21:11 PST by Nikita Vasilyev
Modified: 2016-12-08 13:14 PST (History)
7 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nikita Vasilyev 2015-12-17 21:11:28 PST 
Chrome DevTools and Firefox DevTools both support console.timeline() and console.timelineEnd().
console.timeline() starts timeline recording and console.timelineEnd() stops it.

https://twitter.com/addyosmani/status/487353570606743552
Comment 1 Timothy Hatcher 2015-12-17 21:13:01 PST 
profile and profileEnd do that for us already. Though we can make these aliases or decide to change profile back.
Comment 2 Nikita Vasilyev 2016-01-26 15:07:47 PST 
Chrome DevTools renamed console.timeline & console.timelineEnd to
console.time and console.timeEnd.

> console.timeline()
< 'console.timeline' is deprecated. Please use 'console.time' instead.
> console.timelineEnd()
< 'console.timelineEnd' is deprecated. Please use 'console.timeEnd' instead.
Comment 3 Radar WebKit Bug Importer 2016-01-26 15:08:02 PST 
<rdar://problem/24356209>
Comment 4 Joseph Pecoraro 2016-01-26 15:16:44 PST 
Hmm, we already use time/timeEnd for a high performance time measurement that already outputs to the console.
Comment 5 Nikita Vasilyev 2016-01-26 15:33:16 PST 
(In reply to comment #4)
> Hmm, we already use time/timeEnd for a high performance time measurement
> that already outputs to the console.

Chrome's time/timeEnd does the same.

timeline/timelineEnd were removed when they switched to a tracing profiler in the
timelines.

https://code.google.com/p/chromium/issues/detail?id=412782

I find it to be a very bad developer experience. I hope we don't do the same
with profile/profileEnd.
Comment 6 Timothy Hatcher 2016-01-26 17:15:46 PST 
(In reply to comment #5)
> (In reply to comment #4)
> > Hmm, we already use time/timeEnd for a high performance time measurement
> > that already outputs to the console.
> 
> Chrome's time/timeEnd does the same.
> 
> timeline/timelineEnd were removed when they switched to a tracing profiler
> in the
> timelines.
> 
> https://code.google.com/p/chromium/issues/detail?id=412782
> 
> I find it to be a very bad developer experience. I hope we don't do the same
> with profile/profileEnd.

They made that change due to architecture problems we don't have. I think we should make time/timeEnd markup the timeline like they do, and just keep profile/profileEnd as-is (start and stop the timeline.) I am hesitant to add timeline/timelineEnd as an alias of profile/rpofileEnd since Chrome deprecated it.
Comment 7 BJ Burg 2016-12-08 13:14:34 PST 
It seems this is not needed for parity, and it's redundant with existing API.