Bug 34861 – Web Inspector: Focusing a resource in the inspector should default to content not header

• Status: RESOLVED
• Resolution: FIXED
• Component: Web Inspector (Deprecated)

[Oliver Hunt]

When i focus a resource in the inspector I am vastly more likely to want to look at the content than i am to want to look at the header, given the inspecotr now shows the header by default i have got an unnecessary and extraneous additional step to make which did not exist in prior versions.

[Timothy Hatcher]

IIRC we remember the tab you last used and show that tab the next time.

If not we should.

[Oliver Hunt]

The first time i go to the resource it should go to the content -- once you've gone there you can save, the problem is the initial default.

[Joseph Pecoraro]

Created attachment 48603 [details]
[PATCH] Default to Content Tab

The initial default is "headers" (from Settings.js):

> this._installSetting("resourceViewTab", "resource-view-tab", "headers");

But the relevant code does look at the last user action (from ResourceView.js):

> _selectTab: function()
> {
>     if (this._headersVisible) {
>         if (WebInspector.settings.resourceViewTab === "headers")
>             this._selectHeadersTab();
>         else
>             this._selectContentTab();
>     } else
>         this._innerSelectContentTab();
> },

Sounds like we should just empty out the default, or change it to something like "content" to make it future proof for more tabs. Patch uses "content".

[Timothy Hatcher]

Comment on attachment 48603 [details]
[PATCH] Default to Content Tab

Joe!

[Joseph Pecoraro]

Committed r54702
	M	WebCore/ChangeLog
	M	WebCore/inspector/front-end/Settings.js
r54702 = a589328be42f4ef10a80d756965b133ab5dc6687 (trunk)

[Pavel Feldman]

(In reply to comment #0)
> When i focus a resource in the inspector I am vastly more likely to want to
> look at the content than i am to want to look at the header, given the
> inspecotr now shows the header by default i have got an unnecessary and
> extraneous additional step to make which did not exist in prior versions.

I am not so sure about the "vastly more likely". I was considering the time panel as a tool for optimizing for the network. User should have all the meta-information such as query parameters, size, timing, headers under the tips of his fingers. We should provide enough information so that he would not even need to reach out for the content itself. Firebug is we me there.

Of course there are other scenarios such as navigating to the error source (Oliver submitted a separate bug on that, no question it should be fixed). And there is a scenario when you just browse resources and hence need their content since you are just exploring. Or you want to see if some resource has been updated (we should actually provide Cache info such as Firebug in that case).

What was your scenario, Oliver?

Wrt this bug. If we are making contents default, it makes sense to swap the tabs.