Bug 117720 - Web Inspector: Rename console.markTimeline to console.timeStamp
Summary: Web Inspector: Rename console.markTimeline to console.timeStamp
Status: RESOLVED DUPLICATE of bug 117810
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL: https://developers.google.com/chrome-...
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2013-06-17 16:33 PDT by Divya Manian
Modified: 2013-06-19 20:54 PDT (History)
5 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 Divya Manian 2013-06-17 16:33:58 PDT 
Chrome & Firefox developer tools use console.timeStamp() so I think WebKit should do the same. Reference: 
https://developers.google.com/chrome-developer-tools/docs/console-api

Currently WebKit implements console.markTimeline() & not console.timeStamp()
Comment 1 Radar WebKit Bug Importer 2013-06-17 16:34:40 PDT 
<rdar://problem/14182215>
Comment 2 Divya Manian 2013-06-17 17:05:50 PDT 
Sorry it was originally done in Firebug, but now there is a bug to do it in Firefox Dev tools too https://bugzilla.mozilla.org/show_bug.cgi?id=884125
Comment 3 Joseph Pecoraro 2013-06-19 16:25:41 PDT 
Sorry I missed this before. WebKit currently supports both console.timeStamp and console.markTimeline; and they do the exact same thing.

It looks like Seokju Kwon just put a patch up to move us off markTimeline internally in bug 117810. We can use this radar to track removing markTimeline entirely.
Comment 4 Joseph Pecoraro 2013-06-19 20:54:20 PDT 
(In reply to comment #3)
> It looks like Seokju Kwon just put a patch up to move us off markTimeline internally in bug 117810. We can use this radar to track removing markTimeline entirely.

Seokju's updated patch removes markTimeline. So lets just dup this to that bug.

*** This bug has been marked as a duplicate of bug 117810 ***