1369691 - Inefficient display for "File" column in "Network" tab in devtools

Status: RESOLVED DUPLICATE of bug 1341155

(DevTools :: Netmonitor, defect, P3)

Description

[kud]

Attachment: network-tab.png

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:55.0) Gecko/20100101 Firefox/55.0
Build ID: 20170601030206

Steps to reproduce:

- Open "network" tab
- Watch "file" column


Actual results:

"file" column doesn't show enough information.

If you've got `/url/path/element/`, it will show `/path/element/`, which is ok, but if you've got `/url/path/element`, it will show `/element/` which is really not enough. See the attachement. 


Expected results:

I think we could have something like displaying the whole url but it's the the beginning of the url which got the ellipsis (cf css attribute), like:

`...ent`
`...th/element`
`...rl/path/element`

depending on the width of the "file" column.

Comment 1

[kud]

For the test, you should/must take any url which has a path/some parameters, not just an url which is the root of a domain.

Like: https://api.segment.io/v1/p. It will be only display "p", which is not really enough understand when you've got lots of url like that in the netmonitor.

Comment 2

[kud]

The problem here is you've got `p, t, i, t, i, t, i, 1, t` etc as urls and I was looking for my request which ends by `/1`.

Comment 3

[Simon Courtois]

This issue renders the File column somewhat useless on its own in the case of a RESTful API where you only get the 'id' part of requests, filling up the column with numbers and not much more.

Maybe providing a 'Path' column that would take everything that follows the domain name would help in this situations.

Thanks ❤️

Comment 4

[Marshall]

Attachment: network_panel_file_column.png

In general, the "priority" / size of the column sizes in the Network Panel often time do not align with the information a developer quickly needs. This is also often times dependent on the size of the network panel and orientation of the Dev Tools on the developer workstation, and is restricted further by smaller displays.

In the attached screenshot, Status and Method columns are given a vast amount of room, compared to the File column, which is often more important to the developer scanning this tool to find a particular request.

Here (https://imgur.com/a/UTl9GCf) is another image showing the lack of importance of the columns. The priority of the Type field width is disproportional to File column both in importance to the developer, and to the data contained within the column.

Comment 5

[Jan Honza Odvarko [:Honza] (always need-info? me)]

(In reply to Marshall from comment #4)

In general, the "priority" / size of the column sizes in the Network Panel often time do not align with the information a developer quickly needs. This is also often times dependent on the size of the network panel and orientation of the Dev Tools on the developer workstation, and is restricted further by smaller displays.

This will be solved by support for "Resizeable columns" that allows the user to set custom width for every column. We are just working on this feature and it should be available soon.

(In reply to Simon Courtois from comment #3)

Maybe providing a 'Path' column that would take everything that follows the domain name would help in this situations.
yes, I think that adding a new 'Path' column is the way to go.

Honza

Comment 6

[Lenka Pelechova]

I think this is a combination of these two bugs:

1. Bug 1341155 Show full path in File column in developer tools
2. Bug 1382058 Showing request details in the Network Monitor causes all of the columns to become unsuitably small

• could it be marked as duplicate?
• could the first bug (Show full path in File column in developer tools) be solved by introducing a checkbox (e.g. Full path) similar to Persist Logs and Disable cache that would allow the developer to check it if they want to display full path in the file column? With the resizable columns there should be enough space for full path if that's desired. It's just a thought...

Comment 7

[Jan Honza Odvarko [:Honza] (always need-info? me)]

Agree, let's close this one.

Honza