Remove NET filter button, logs from Web Console

RESOLVED WONTFIX

Status

defect
P3
normal
RESOLVED WONTFIX
6 years ago
11 months ago

People

(Reporter: rcampbell, Unassigned)

Tracking

(Blocks 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
We have a netmonitor now. We should remove the output from the console and remove the filter button.
Duplicate of this bug: 909755
One nice thing about Net output in the Console is that you can easily correlate the timing of network activity with other Console stuff, like logging, which can help diagnose some issues.  Since we don't yet have a detailed timeline of general page activity, Net logging in the Console remains handy in a few cases.

However, I do agree it is typically noise, and I usually turn it off.
Thanks for the bug report. This seems to be a duplicate of an older bug report from Heather, if I correctly remember - I cannot find the bug now.

Things to consider:

- blockers of bug 861335.
- bug 868382 and similar memory use issues.
(Reporter)

Updated

6 years ago
Duplicate of this bug: 909800
(Reporter)

Updated

6 years ago
Blocks: 909803
Priority: -- → P3
I agree with J. Ryan in comment 2. Seeing personally logged debug data next to (especially) asynchronous requests is useful, and probably a debugging workflow a number of developers have adopted and have come to expect from the console over the years. Removing this information from the console would probably disrupt a lot of that convenience. I created bug 972655 several weeks back, "Console's 'Net' filter should have option to distinguish sync from async requests," to try and address the noise, but still make the debugging experience familiar.
See Also: → 972655
This is likely to get more attention now, with focus on Firebug Gaps.

I propose that we do indeed remove the Net Filter button, but that we leave a way to turn on XHR requests in the console.

Justification:

* We'd like to clean up the console which means fewer messages
* We've already got the network panel for detailed network analysis
* There are many requests for XHR in the console, and it's what everyone else does AFAIK

The XHR in the console switch should be in the options panel and off by default.
Blocks: firebug-gaps
If the "Net" filter button is removed, what will be the default for displaying its child options, such as "Errors" and "Warnings"? Will they just be on by default, or will the ability to toggle them on or off be located elsewhere? The latter does not sound convenient.
I'm not actually sure what network warnings and logs are for. Anyone know?

I think we should show network errors in the console (or wherever we normally display errors - we've talked about having a separate panel for that)
I think we should just disable it by default (if that isn't already the case). Agree with folks who say that it can be useful to see in the context of logged messages.
Network logs are for successful requests. Network warnings are for requests from mixed content - eg. http loading https and vice-versa. Network errors are for requests with known error codes.

Network logs are disabled by default. I am not convinced this bug is related to firebug gaps - I'd like to understand why. Like Nick and others, I believe the console net logs, combined view, does offer benefits not available in netmonitor. Mixed content and errors are not as clearly visible either.

We should show XHR requests by default, and that's a firebug gap which we can easily fix, see my latest comments in bug 972655. We should also remove the dreaded net panel popup.

Comment 11

4 years ago
Is it WONTFIX considering we want to make improvements to the existing NET filter ?
(In reply to Tim Nguyen :ntim (busy, email me instead) from comment #11)
> Is it WONTFIX considering we want to make improvements to the existing NET
> filter ?

In regard of bug 1211525 being implemented lately, this is definitely WONTFIX. Instead of removing the button completely, I'd just remove the 'Warnings' filter (see below) and move the button more to the right, as I assume it is used less than other filters.
Therefore ni'ing the related persons regarding comment 11.

(In reply to Joe Walker [:jwalker] (needinfo me or ping on irc) from comment #6)
> This is likely to get more attention now, with focus on Firebug Gaps.
> 
> I propose that we do indeed remove the Net Filter button, but that we leave
> a way to turn on XHR requests in the console.
> 
> Justification:
> 
> * We'd like to clean up the console which means fewer messages

This could also be achieved by changing the filter defaults. Though the network filters are already set to only list errors and warnings.

> * We've already got the network panel for detailed network analysis

I don't understand why but there is a big user demand for displaying network requests within the Console panel (see bug 1211525 & Co.)

(In reply to Joe Walker [:jwalker] (needinfo me or ping on irc) from comment #8)
> I'm not actually sure what network warnings and logs are for. Anyone know?
> 
> (In reply to Mihai Sucan [:msucan] from comment #10)
>> Network logs are for successful requests. Network warnings are for requests
>> from mixed content - eg. http loading https and vice-versa. Network errors
>> are for requests with known error codes.

The message about blocked mixed content falls under the category 'Security' > 'Errors', so obviously 'Network' > 'Warnings' doesn't do anything anymore.

Sebastian

[1] https://developer.mozilla.org/en-US/docs/Tools/Web_Console/Console_messages#Security
Flags: needinfo?(mihai.sucan)
Flags: needinfo?(jwalker)
Flags: needinfo?(jryans)

Comment 13

3 years ago
:sebo, check console.mihai() to see why cleared this ni.
Flags: needinfo?(mihai.sucan)
Lin, I think you're the best person for this?
Flags: needinfo?(jwalker)
Flags: needinfo?(jryans)
Flags: needinfo?(lclark)
Helen came up with mock-ups a few months back. The plan is to move severity to the top level instead of category. We had not planned to remove the network logs from the console. I'm going to mark this as WONTFIX. We may decided to do it later, but we can create another issue at that point.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Flags: needinfo?(lclark)
Resolution: --- → WONTFIX

Updated

11 months ago
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.