[Webkit-unassigned] [Bug 37215] Web Inspector: be more explicit about resource loading errors

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=37215





--- Comment #11 from Andrey Kosyakov <caseq at chromium.org>  2010-04-08 08:41:40 PST ---
(In reply to comment #9)
> re: comment 2: "Do you have a use case in mind that where a resource loading
> failure is "normal" and would cause lots of messages to be logged?"
> 
> I didn't mean to imply I thought resource loading was "normal", more that I've
> heard other complaints about excess messages being printed to the console; for
> example XHR completion messages.  

I disable logging XHR messages to console a few days ago, so there's going to
be way less noise now. The key difference to logging resource failures is that
these are of much greater importance and usually mean something went wrong --
much as JS errors that we also log there.

> re: comment 4: "There is already the HTTP status code for showing failure in
> the Headers tab."
> 
> Which isn't appropriate if the resource never got an HTTP response.  Examples:
> XHR requests that result in xhr.status == 0 (when you can't connect to the
> server, and probably other cases); resource loads in an app-cache environment
> where the resource isn't listed in the manifest (no request is ever made of the
> resource, but it shows up in the resource list - as it should).

That's not the case where we used to log those messages -- they were logged
only when we got an erroneous HTTP response.

> In both of these cases, there is additional information that we can provide, in
> theory, about why the resource wasn't loaded.  Let's say we can actually
> determine the reason why an xhr.status == 0 occurred, say ECONNREFUSED when
> trying to access the resource - where would we provide that information?  The

I like the idea to provide details on network-level failures on resource tab --
I'll have a look.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.