Bug 117720
| Summary: | Web Inspector: Rename console.markTimeline to console.timeStamp | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Divya Manian <divya> |
| Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | graouts, joepeck, seokju, timothy, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | https://developers.google.com/chrome-developer-tools/docs/console-api | ||
Divya Manian
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()
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/14182215>
Divya Manian
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
Joseph Pecoraro
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.
Joseph Pecoraro
(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 ***