I didn’t find a way to debug Greasemonkey scripts with the Firebug extension.
Does anyone know how to do this ?
Thanks.
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Updatier: The Mene+Shuman fix now is busted with Firefox 30 and Firebug 2. Firefox 31 may provide workarounds (will investigate). In the meantime, use the “General workaround strategies” listed below.
Update: This answer is now obsolete.
If you open
about:configandset
extensions.firebug.filterSystemURLstofalsethen you can use Firebug to debug the Greasemonkey script just like any other.
This works irregardless of the
@grantmode.See Mene’s answer — with an assist from Shuman.
Old answer:
Because Greasemonkey operates in a sandbox, Firebug cannot see it. There is no easy way around this.
General workaround strategies:
Test all parts of a GM script that don’t use
GM_functions, in Firebug’s JavaScript console first. Minimize use ofGM_functions and don’t useGM_log()at all.All of Firebug’s
consolefunctions work great from within a GM script.