Topic: how to compile a greasemonkey script into .XPI for Firefox 2.0+

Interesting problem. I discovered that the compiled version of your original MVT Vendor Detector script would work if a trailing newline was added to the source code, otherwise the error message you listed occurred on all sites. In other words, if you add a line after '//alert('done');', then the XPI will work properly on the Google test site listed in your script comment, highlighting several matches.

Topic: how to compile a greasemonkey script into .XPI for Firefox 2.0+

I've not looked at your code for more than 10 seconds to glance down it, and I have a quick question -- why is 'messageDiv.innerHTML' (towards the end) spread over so many lines? Is this the way the forum's formatted it, because I'm not sure but that might cause problems if that's how it is in your script.

Topic: how to compile a greasemonkey script into .XPI for Firefox 2.0+

Greasemonkey scripts are wrapped in a function call. Perhaps you've unbalanced {}s somewhere else in your code? Do you normally see error messages from GM scripts?

Topic: how to compile a greasemonkey script into .XPI for Firefox 2.0+

The one at http://arantius.com/misc/greasemonkey/script-co... definitely works with Firefox 1.5 and 2.0.