RESOLVED DUPLICATE of bug 125909 14378
Timeline view's scale should be adjustable 
https://bugs.webkit.org/show_bug.cgi?id=14378
Summary Timeline view's scale should be adjustable
Adam Roben (:aroben)
Reported 2007-06-24 22:49:20 PDT
The Inspector's timeline view should be zoomable. If many resources load very quickly at approximately the same time, it is hard to see the exact sequence (though the sorting of the timeline view helps). It would be nice if you could zoom in (essentially increase the time scale) so that you can see in greater detail the order of events.
Attachments
Work in progress patch (4.53 KB, patch)
2008-08-24 17:36 PDT, Anthony Ricaud 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Adam Roben (:aroben)
Comment 1 2008-01-29 11:00:25 PST
<rdar://problem/5712830>
Anthony Ricaud
Comment 2 2008-08-24 17:36:42 PDT
Created attachment 22968 [details] Work in progress patch This is just a beginning with lots of bugs. I'd like some comments on the way to do this cause I'm not sure to do it the right way.
Keishi Hattori
Comment 3 2008-08-24 21:32:30 PDT
I tried to do this and I realized this
Pavel Feldman
Comment 4 2009-10-31 14:29:14 PDT
I am essentially doing the same thing. But I approach it differently: 1. Nothing should be resources-specific: Resources and Timeline now share underlying component. 2. I am converting AbstractTimelinePanel to TimelineView. There will be several of those in one panel. 3. Timeline Panel (and after some time Resources Panel) will consist of two stacked TimelineViews: [BirdsEyeTimelineView] [WindowTimelineView] First will control the second and contain filters and summaries (as in Timeline mock). This has been discussed on the IRC, but I did not manage to put the bug together. Happy to shard the effort if we find a way!
Blaze Burg
Comment 5 2014-01-12 11:21:22 PST
The timeline rewrite underway has zoomable views.
Timothy Hatcher
Comment 6 2014-01-18 00:35:54 PST
*** This bug has been marked as a duplicate of bug 125909 ***
Note You need to log in before you can comment on or make changes to this bug.