Bug 38467 - Web Inspector: Implement source code 'drawer' for Timeline and Profiles panels.
Summary: Web Inspector: Implement source code 'drawer' for Timeline and Profiles panels.
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (Deprecated) (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-03 08:32 PDT by Pavel Feldman
Modified: 2014-07-21 10:12 PDT (History)
8 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pavel Feldman 2010-05-03 08:32:20 PDT
While working with Timeline and Profiles, we often need to navigate to source code and get back to the original panel. Instead of switching contexts entirely all the time, it would be nice to have a drawer with the source code popping on navigate action. Implementing yet another drawer does not look good from usability standpoint (confuses with console), so I am filing this alternative mock for your consideration. It is a vertical drawer, that has a 'hide' button (and also should have 'pin' button that would do the navigation to appropriate panel and switch context).
Comment 1 Timothy Hatcher 2010-05-03 13:01:33 PDT
I'd rather just fix the panel navigation issues. I really don't want multiple ways to view the same source code (Scripts and Resources are it).

Drawers (vertical or otherwise) are bad when docked, so we should not have any more drawers unless it truely is somethng that should be accessed across multiple panels. And I don't think this fits.
Comment 2 Pavel Feldman 2010-05-04 05:21:11 PDT
(In reply to comment #1)
> I'd rather just fix the panel navigation issues. I really don't want multiple
> ways to view the same source code (Scripts and Resources are it).
> 

By navigation you mean ability to go back to previous panel / state?

> Drawers (vertical or otherwise) are bad when docked, so we should not have any
> more drawers unless it truely is somethng that should be accessed across
> multiple panels. And I don't think this fits.

I was profiling something and found myself switching between profile and scripts panels a lot. I was clicking through links on the profile fairly quickly and was looking for the methods I could optimize. And every time I needed to go back and find a profile node I was processing. Same happened to me while working with timeline. I really think we should have a way of viewing (previewing) source while traversing the trees / lists as if that tree was a file system browser in a classical IDEs. Otherwise, it takes too much time to get back into the context.