Is this greasemonkey getting confused because we have a url ending in .js whose resource has content-type text/html? Sounds like a greasemonkey bug to me! Like this one: http://greasemonkey.devjavu.com/ticket/14
We can probably come up with some workaround though.
Is this greasemonkey getting confused because we have a url ending in .js whose resource has content-type text/html? Sounds like a greasemonkey bug to me! Like this one: http:// greasemonkey. devjavu. com/ticket/ 14
We can probably come up with some workaround though.