Bug 90288 - Web Inspector: Re-organize of resource tree panel
Summary: Web Inspector: Re-organize of resource tree panel
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: 2012-06-29 09:26 PDT by Rob Colburn
Modified: 2012-08-08 21:32 PDT (History)
10 users (show)

See Also:


Attachments
Updated Resources panel (15.38 KB, image/png)
2012-06-29 09:26 PDT, Rob Colburn
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rob Colburn 2012-06-29 09:26:02 PDT
Created attachment 150195 [details]
Updated Resources panel

I propose the following changes.  I'm comparing to build in the current Chrome Canary (screen capped in attached).

1. Rename "Frames" to "Sources".  It doesn't make sense to call it "Frames", since there are more than frames listed.  Also, I believe it's the case that there is always a root frame (right?), even in a frameset page there is a master frame.

2. Rename the "Root Frame Host" to "Frames", since all of the frames are children of it anyway.

3. Move the "Root Resources" (Fonts, Images, Other, Scripts, Stylesheets, ...) up one level in the hierarchy.  So it's now under the "Sources" node.

4. Prepend the domain to each child frame url.  While the end of the url and the domain are both very useful, I suggest "DOMAIN.../END_OF_URL"

5. Add a title attribute on the Frame folders, so there's for a tooltip for the full URL.  You can find that currently, but it's an extra step.

Put these together and we should end with something like right side the screenshot.
Comment 1 Pavel Feldman 2012-06-29 11:22:50 PDT
(In reply to comment #0)
> Created an attachment (id=150195) [details]
> Updated Resources panel
> 
> I propose the following changes.  I'm comparing to build in the current Chrome Canary (screen capped in attached).
> 
> 1. Rename "Frames" to "Sources".  It doesn't make sense to call it "Frames", since there are more than frames listed.  Also, I believe it's the case that there is always a root frame (right?), even in a frameset page there is a master frame.
> 

These are in fact Frames and their Resources, Sources are in the Sources panel, we don't want to add extra confusion here.

> 2. Rename the "Root Frame Host" to "Frames", since all of the frames are children of it anyway.
> 
> 3. Move the "Root Resources" (Fonts, Images, Other, Scripts, Stylesheets, ...) up one level in the hierarchy.  So it's now under the "Sources" node.
> 

"Root Frame Host"? Where is it? Or you mean its domain? So you are suggesting that main frame kinda becomes the root node? We can do that, please file a bug for that.

> 4. Prepend the domain to each child frame url.  While the end of the url and the domain are both very useful, I suggest "DOMAIN.../END_OF_URL"

Sounds good, please file a bug on this.

> 5. Add a title attribute on the Frame folders, so there's for a tooltip for the full URL.  You can find that currently, but it's an extra step.
> 

Sure, could be the same bug as above.

> Put these together and we should end with something like right side the screenshot.


Do you have a patch for this? Are you going to come up with one?
Comment 2 Rob Colburn 2012-08-08 21:32:02 PDT
Personally, I'm still a bit intimidated by the Webkit's development process.  Someday, I'll read up and figure it out.

Filed: #93576, #93577