On 2011-01-28 6:51 AM, Boris Zbarsky wrote:
The DOM selector APIs (matchesSelector, querySelector, querySelectorAll) throw when the selector can't be parsed. Given that, do we still want to report parse errors as warnings to the error console? Doing this apparently causes at least some people angst: see http://bugs.jquery.com/ticket/7535
I am generally for changes that reduce the amount of useless chatter in the error console.
(I can see the argument for reporting it, since the DOM exception gives no indication of where the error occurred, by the way.)
We could put that information into the DOM exception, couldn't we? And pull it back out and log it if and only if the exception is not caught.
(While I'm complaining, this isn't exactly the same problem, but the error console messages we produce for uncaught JS exceptions that arise from DOM APIs are full of XPCOM jargon, so they give the impression that we're reporting some kind of internal failure rather than a bug in web page JavaScript.)
zw _______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
