On 1/31/11 11:35 AM, Mike Shaver wrote:
On Mon, Jan 31, 2011 at 6:16 AM, Boris Zbarsky<[email protected]> wrote:
[09:01:04.453] uncaught exception: [Exception... "An invalid or illegal
string was specified" code: "12" nsresult: "0x8053000c
(NS_ERROR_DOM_SYNTAX_ERR)" location: "file:///tmp/test.html Line: 14"]
Of course that's full of the XPCOM jargon I was complaining about
Apart from the "nsresult" bit, the hex code for the nsresult, and the
"NS_ERROR" prefix, is there other jargon?
The extra [Exception...] and code 12, at least.
"12" is the per-spec value of DOM_SYNTAX_ERR, which is the exception
being thrown (see the DOMException interface in DOM Core). It's not
xpcom anything.
In general we also don't say which method is being called incorrectly, IIRC.
Yes, in this case. I'm not saying this exception message doesn't have
major issues, which we should fix! It's just that most of those issues
have nothing to do with "xpcom".
Hmm. We have bugs on that, for what it's worth; it's not that easy last I
checked.
Seems like a last-error singleton would work, in concert with our
single-threadedness?
I think the hard part was finding all the fiddly xpconnect bits that
needed fixing (well, and the fact that exception throwing can nest and
such).
-Boris
_______________________________________________
dev-tech-layout mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-layout
