On 20/10/2011 21:35, Dave Land wrote:
On Oct 20, 2011, at 12:28 PM, Anthony Lieuallen wrote:
On 10/20/2011 03:18 PM, Dave Land wrote:
... some pages that do NOT
match the @include and @match lines, ...
// @match *://*.facebook.com/*
// @include *://*.facebook.com/*
...
Which pages, exactly? That include will effectively match any page that has the string
".facebook.com/" anywhere in it. E.G. if a query string variable contains a
facebook URL in it, perhaps as a redirection/next page target.
Anthony,
Thanks for the lightning-quick reply. Good thought, but the other pages that
are running the script don't have facebook.com in the URL anywhere — for
example, one of them is the time-tracker app at harvestapp.com for my job. The
URL is very short, and doesn't have facebook anywhere in it.
I'll be sure to pass along word if I figure out what's up. Do you know of a way
to debug something like this?
Incidentally, since FB changed their layout, the script doesn't work, anyway
;-).
Dave
Could be a few things I guess.
Maybe an alert(document.location.href) or similar will help in
debugging? Might catch a couple iframes / whatever that don't have a
"navIdentityPic" that you weren't expecting? An
if(document.getElementsByClassName("navIdentityPic").length) {} would
also help pinpoint where the issue is.
My second thought is that it might be an issue with AJAX and the nodes
that you're expecting to be there haven't yet loaded, and the 500ms
timeout isn't long enough to beat the race condition? Without testing it
myself I'm not sure. Perhaps temporarily change it to a setInterval() ?
--
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.
