On 4/9/10 12:01 PM, John J Barton wrote:
On Apr 9, 11:50 am, "Brian L. Matthews"<[email protected]>  wrote:
On 4/8/10 11:56 PM, Honza (Jan Odvarko) wrote:>>  I wanted to try out 
XPathResult logging so I installed this, but I'm
working on a Greasemonkey script, and it appears that
console.log(object) doesn't make the [object Object] click able, and
console.dir doesn't work at all in Greasemonkey scripts. Is that on
purpose? Both worked in 1.5.3 with the same Greasemonkey script
(although of course without the enhanced XPathResult display). I'm using
Firefox 3.6.3 and Greasemonkey 0.8.20100408.6.
I have installed Firefox 3.6.3 + Firebug 1.6a9 + Greasemonkey
0.8.20100408.6.
and tried following test case:
http://getfirebug.com/tests/content/console/api/log-xpathresult.html
Sorry, I wasn't very clear. console.log and console.dir fail only when
called from a Greasemonkey user script, they work fine (and the
XPathResult display is nice, thanks!) from regular pages. So the URL
above works as expected. Here's a test case for the failure in a user
script:
I guess that you need to contact Greasemonkey. I suppose they are
implementing console.log in the user scripts. We changed the console
implementation in 1.6a9, but not by a lot. There is probably some
small change needed.

I'll contact the Greasemonkey people, although an identical version of Greasemonkey works fine with 1.5.3, so something changed in 1.6a9 (or maybe earlier, I didn't try any other 1.6's) that broke things. Maybe it's because Greasemonkey is doing something wrong and 1.5.3 just happened to work while 1.6a9 has tightened things up, but I'd still think it important to maintain backward compatibility, particularly with such a widely used extension as Greasemonkey.

Brian

--
You received this message because you are subscribed to the Google Groups 
"Firebug" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/firebug?hl=en.

Reply via email to