Web Console: normal GET requests should show up under Net/Log, not Net/Error

RESOLVED FIXED

Status

P1
normal
RESOLVED FIXED
8 years ago
2 months ago

People

(Reporter: bj, Assigned: pcwalton)

Tracking

Trunk
x86_64
Linux

Firefox Tracking Flags

(blocking2.0 final+)

Details

(Whiteboard: [Web-Console-Testday][fixed by bug 605621])

(Reporter)

Description

8 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101206 Ubuntu/10.10 (maverick) Firefox/3.6.13 ( .NET CLR 3.5.30729; .NET4.0C)
Build Identifier: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b8pre) Gecko/20101209 Firefox/4.0b8pre ID:20101209030340

I've tried several web page loads, and the filter Net/Log is always empty, and Net/Error contains non-error network requests.

Reproducible: Always

Steps to Reproduce:
1. Open Web Console.
2. Load google.com in the tab.
3. Click the down arrow next to "Net" in the Web Console filter bar and un-check Error.
Actual Results:  
All the network requests go away.

Expected Results:  
Network requests causing errors (e.g., don't load) should go away, but non-error requests should not go away.
(Reporter)

Updated

8 years ago
Whiteboard: [Web-Console-Testday]
Version: unspecified → Trunk

Updated

8 years ago
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 1

8 years ago
Confirmed: the network filtering is not doing the right thing at all. That said, it's possible that this may be fixed by other patches (I'll see if Patrick or Mihai have any comments on that).
Assignee: nobody → pwalton
Blocks: 593956
blocking2.0: --- → ?
Priority: -- → P1
(Assignee)

Comment 2

8 years ago
This is fixed by bug 605621 I believe.
Agreed. This bug should be fixed by the work Patrick did in bug 605621. I'll retest tomorrow to make sure, but that's one of the things I asked for, when I provided my feedback. I believe Patrick fixed it. ;)
blocking2.0: ? → final+
Whiteboard: [Web-Console-Testday] → [Web-Console-Testday][fixed by bug 605621]

Comment 4

8 years ago
The code from bug 605621 has landed and I just confirmed that this is fixed.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED

Updated

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