1957272 - Failed (404) favicon request is categorized as HTML and displayed when filtering to show HTML only

Status: RESOLVED INVALID

(DevTools :: Netmonitor, defect)

Description

[[:jaborandi]]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:136.0) Gecko/20100101 Firefox/136.0

Steps to reproduce:

1. Open new tab
2. open DevTools / Network
3. click HTML in the filter, to view only HTML requests
4. go to example.com

Actual results:

2 requests: for / and for favicon.ico get displayed in the log

Expected results:

only the first one should be displayed

note: if you change to showing only Images, favicon will be displayed too - correctly this time

Comment 1

[Julian Descottes [:jdescottes]]

Thanks for filing, this happens on example.com because the request to the favicon fails with a 404 which is return with a text/html content-type.
I think the current behavior is fine.

Comment 2

[[:jaborandi]]

:jdescottes it really isn't

filters are a UI control that allows us to focus on specific things, in this case - specific types of resources
the specifics of the related error handling should no affect that
underlying implementation means that image that is not available is substituted with a HTML
it could be the opposite - a HTML not available substituted with image - it doesn't really matter

when you filter by HTML and filter OUT images you want to focus on HTML documents, and this implementation makes it impossible

what's the gain? as a side effect, you might be able to filter images that are not available? well it's a dubious benefit, probably not reliable, and if someone does want to list all images requests that ended up in 404 their logical attempt would be to view all images with status code 404 - not to view all html documents (and then search for images among them manually, without possibility to filter)

current implementation is formal and it doesn't do what it intends to do

anyway, just wanted to comment here to have the reasoning to later copy it to the new bug (possibly request for enhancement)

if you want unavailable

Comment 3

[[:jaborandi]]

to give you a obvious more practical example:

you are debugging a page with 10 images
5 of them are not available - return 404
right now you want to focus on HTML
you filter to view HTML only yet the list is cluttered with multiple images
you know there are unavailable images - yet you cannot or don't want to do anything about it now, you are focusing on different thing - yet the interface things otherwise

yes, there's a reason why interface does it, but it is useless for what it is intended to do, agree?

Comment 4

[[:jaborandi]]

*thinks