I got around this issue by using: window.setTimeout(linkifyfb, 1000);
And then in linkifyfb, at the end, I call it once again: window.setTimeout(linkifyfb, 1000); So my function runs every second. This worked great for my script, since FB is so ajax heavy, it allows it to catch new elements. See my script here if you'd like: http://subprocess.net/twitterifyfb.user.js -- not submitted to userscripts yet, still testing it and tweaking it. I tried some other options... One thing you can do is use something like: var hash = ''; document.addEventListener("DOMNodeInserted", fbNodeInserted, false); function fbNodeInserted() { if ( hash != location.href ) { hash = location.href; fbLinkClicked(); } } function fbLinkClicked() { //do your thing here. } Hope that helps... I was quite frustrated with this myself at first too- Ryan On Aug 25, 7:47 pm, dr meehan <[email protected]> wrote: > For some reason, Facebook has an annoying habit of adding a fragment > identifier (hashtag + keywords) following a URL if I navigate away > from the home page and return to it by clicking the Facebook icon or > clicking the home button. This would not be a problem, except that in > so doing it destroys my Greasemonkey scripts-none of them work. In > theory, they still should from what I set as the URLs for them to work > on. But they don't. Has anyone experienced this? Any fixes for this > out there? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
