column widths are not adjustable on Network tab of devtools
open a page in SM, F12, Network tab, try to adjust column widths - no sizer mouse pointer, click+drag doesn't do anything
column widths are not adjustable on Network tab of devtools
-
- Posts: 381
- Joined: November 13th, 2004, 7:03 pm
- Location: Alabama
- therube
- Posts: 21698
- Joined: March 10th, 2004, 9:59 pm
- Location: Maryland USA
Re: column widths are not adjustable on Network tab of devto
Confirmed.
(FF 91, or 92 or whatever it is, does allow width adjustment.)
(FF 91, or 92 or whatever it is, does allow width adjustment.)
Fire 750, bring back 250.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript
-
- Posts: 1361
- Joined: December 15th, 2015, 1:20 pm
Re: column widths are not adjustable on Network tab of devto
devtools got updated lately. The real question is if it did work before? Otherwise it is an enhancement not a bug. If it works differently in Firefox 101 is not relevant here. Just means it was changed later then.
- therube
- Posts: 21698
- Joined: March 10th, 2004, 9:59 pm
- Location: Maryland USA
Re: column widths are not adjustable on Network tab of devto
I'm not seeing where it did.did work before?
Not in various 2.53.1 .. .9 .. 2.53.10 Build 20210829222501, nor in 2.49.5.
Fire 750, bring back 250.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript
-
- Posts: 381
- Joined: November 13th, 2004, 7:03 pm
- Location: Alabama
Re: column widths are not adjustable on Network tab of devto
For reference, the columns on the Storage tab are adjustable.
To be sure, missing a bug on release (or latency) does not negate that a defect is a defect. The planned design determines if something is a defect. And I don't have access to the design docs to make this determination
To be sure, missing a bug on release (or latency) does not negate that a defect is a defect. The planned design determines if something is a defect. And I don't have access to the design docs to make this determination