Comment 6 for bug 14576

qa to me +cc mpt

changed subject to clarify what is needed.

(I've read most of the related error bugs, and this one is closest to the RFE I
wanted to file...)

I think what is needed is an error mode (that should be prefs pickable), that
creates a error list window. Errors would get sent to it (the way vacation
messages pile up in AIM...), but would be non-blocking, not waiting for user
confirmation.

For my purposes, this would ideally over-ride all the other types of error
behavior we have discussed in various bugs (send to a page, send to a dialog,
display broken icon for missing inline graphic, etc).

Power users and network analysts would love this feature because it gives them
total visibility to what network problems occur.

It would also be great for ibench and browser buster testers, because
intermittent errors would not lock up the test until a human clears the error
dialog.

My thinking here is that our current error handling reflects a misunderstanding
about errors needing blocking network access. Most network errors are transient,
and they do not actually block further network access. They do however, block
the user experience, because you assume that the browser was pulling something
that a user wanted to see.

There are some potential problems (like infinite errors logged when a router
goes down w/ a continuous test), but I think these could be worked out...