ecma/ExecutionContexts/10.2.2-1.js Exception... "Cannot find interface information for parameter arg 0 [nsIDOMWindowInternal.pkcs11]" nsresult: "0x80570006 (NS_ERROR_XPC_CANT_GET_PARAM_IFACE_INFO)" location: "JS frame :: http://test.mozilla.com//tests/mozilla.org/js/ecma/ExecutionContexts/10.2.2-1.js :: <TOP_LEVEL> :: line 91" data: no]; and similarly for: ecma/ExecutionContexts/10.2.2-2.js ecma_2/Statements/forin-002.js js1_5/Array/regress-108440.js js1_6/extensions/regress-455464-01.js js1_6/extensions/regress-455464-02.js js1_6/extensions/regress-455464-03.js js1_6/extensions/regress-455464-04.js js1_6/extensions/regress-475144.js js1_7/extensions/regress-455982-01.js js1_7/extensions/regress-455982-02.js js1_8/extensions/regress-452476.js js1_8/extensions/regress-476427.js js1_8_1/trace/trace-test.js all show this error in the browser. occurs in mozilla-central and tracemonkey. regressed by bug 326628, http://hg.mozilla.org/mozilla-central/rev/eea9639048b8 sensitive since bug 326628 is.
This doesn't need to be private. The problem seems to be that because nsIDOMpkcs11 is only a forward-declared interface and never exists, that we can't return it from a method, even though we only ever return "null". We could either re-add nsIDOMpkcs11 and not implement it anywhere (which seems silly, but it will at least fix the bug, as well as bug 487960), or we could have xpconnect not look for interface info until after it got an object to wrap. The first definitely seems easier, but I'm open to suggestions.
Created attachment 372392 [details] [diff] [review] Remove leftover references to nsIDOMPkcs11, rev. 1 On trunk we can just remove the extra references. On the branch, I just left nsIDOMPkcs11.idl in the tree even though there are no implementers.
This is only present on trunk, not a branch blocker.
This is present on tracemonkey. I need it fixed there as well.
v 1.9.2. thanks.
Gregory, that's a different bug (and was caused by bug 326628, not this one). Please file it separately and cc me.
Backed this out with bug 326628... I'll just leave this bug closed and make sure to re-land it if appropriate when bug 326628 relands.