On Oct 20, 2011, at 4:20 PM, Anthony Lieuallen wrote:

> On 10/20/2011 04:35 PM, Dave Land wrote:
>> Do you know of a way to debug something like this?
> 
> I'd start by logging/alerting/something "document.location.href" in the 
> script to see exactly where it's firing.  I'm starting to guess something 
> like an iframe for a like button.  But without actually seeing it happen I 
> can only guess.

I thought you were onto something with the iframe suggestion: I've had issues 
with that before, when scripts appeared to fire off two or three times on a 
page. But not this time. The script was triggered on 
https://liveworld.harvestapp.com/daily, which doesn't seem to match 
*://*.facebook.com/*.

It also is triggered on Google, such as this:

https://encrypted.google.com/search?num=100&hl=en&newwindow=1&safe=off&sout=1&as_qdr=all&q=sicut+cervus+desiderat+translation&oq=Sicut+cervus+desiderat+&aq=0&aqi=g4g-v6&aql=1&gs_sm=e&gs_upl=35295l37325l0l38480l11l10l4l3l5l0l150l336l1.2l3l0

I realize that this is probably a question for the Google Chrome bug tracker, 
so I'll ask it there, too.

Thank you for your help so far, Anthony.

Dave

-- 
You received this message because you are subscribed to the Google Groups 
"greasemonkey-users" 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/greasemonkey-users?hl=en.

Reply via email to