Erik Vold

So because of GM issue 1086 and the GM 0.9 roadmap it appears to me that the manage dialog is being removed.

So assuming that WM is doing the same, I think we...

An alternative would be to put xhr code into api.jsm, as it's only used there anyway. This way we'd stick to the current philosophy: api.jsm includes all API f...

One solution would be to export Components.stack.filename from xhr.jsm in some variable which is added to the if check started on line 177. The xhr.jsm is only...

Well I was able to identify the problem..

GM /components/greasemonkey.js line 48 is stack.filename != gmSvcFilename where gmSvcFilename is file:///C:/github/gr...

bah I can't seem to edit my previous comment.. -1 point for lighthouse.. I meant apiLeakCheck* where I said "api check function"..

Well the errors above are generated when the GM_getValue() function does the api check, and the api check function does appear to be slightly different..

• For G...

I've made a simple test case here which works in GM and produces the following error in WM:

Error: Webmonkey access violation: file:///C:/github/webmonkey/src/m...

This userscript produces an error in WM and is fine in GM. The following error:

Error: Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIScr...