As we add more and more console messages to educate developers about errors on their pages, we run the risk of overwhelming them. Some examples include: * incorrect MIME type errors * Sandbox violations (see bug 103255 for discussion) * CSS errors (see bug 19236 and (more recently) bug 102750 for discussion) It would be nice if we were able to present these sorts of errors to developers in a way that encouraged understanding rather than a potentially ignored flood.
+ojan One short-term change that might help pave the way for this is to mark the messages that we think would make sense to separate out. We could create a new message level, even lower than Tip, and surface a new checkbox on the bottom of the console to display them. It might even make sense not to display them by default. *shrug* I don't think that's the right longer-term solution, but if there's interest I'll spin off a separate bug for an experiment in that direction.
I don't have strong opinions on the implementation. I've just been very frustrated as a web developer when I miss JS exceptions in my code because they're hidden in a pile of console warnings that I can't hide.
(In reply to comment #1) > +ojan > > One short-term change that might help pave the way for this is to mark the messages that we think would make sense to separate out. We could create a new message level, even lower than Tip, and surface a new checkbox on the bottom of the console to display them. It might even make sense not to display them by default. *shrug* Looks like this was done in https://bugs.webkit.org/show_bug.cgi?id=103781. caseq, yurys: What do you think about migrating other messages into the Debug level?
This work is being revived in the form of different "Analyzer" instances in the current inspector. Tracked here: https://bugs.webkit.org/show_bug.cgi?id=136515