Bug 128617 - Web Inspector: main timeline view should not resize when details sidebar is shown
Summary: Web Inspector: main timeline view should not resize when details sidebar is s...
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Matt Baker
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2014-02-11 13:12 PST by BJ Burg
Modified: 2015-05-04 14:13 PDT (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description BJ Burg 2014-02-11 13:12:15 PST
The top overview timeline doesn't resize when details sidebar appears, but the bottom timeline does resize. It's jarring, and I think the overview and main view should have the same behavior if possible.
Comment 1 Radar WebKit Bug Importer 2014-02-11 13:12:38 PST
<rdar://problem/16040319>
Comment 2 Timothy Hatcher 2014-02-11 15:31:02 PST
The top timeline is not expressed as a start and end time, it is expressed as a start time and seconds per pixel. So resizing the window will not grow or shrink the view. It is just revels more or less time. The bottom view is bound by a start and end time (from the selection), so it will grow and shrink.

Showing the sidebar can be special cased to adjust the seconds per pixel on show/hide to give the illusion needed. But I'm not sure I agree with that.
Comment 3 BJ Burg 2014-02-11 15:34:39 PST
I can see why that makes sense, it's just visually jarring if you are hoping to cross reference things on the sidebar against the timeline and then everything jumps.
Comment 4 Brian Burg 2015-04-28 10:29:06 PDT
I think we should revisit this, now that the Rendered Frames sidebar causes the timeline overview to jump position.
Comment 5 Timothy Hatcher 2015-04-28 10:59:07 PDT
The Rendered Frames details sidebar will soon go away. It will be moved to the empty space in the navigation sidebar.
Comment 6 Matt Baker 2015-05-04 14:13:12 PDT
This is no longer an issue after https://bugs.webkit.org/show_bug.cgi?id=144346.