aProgress.isLoadingDocument is probably what is tripping it up https://developer.mozilla.org/en/nsIWebProgress
This is the start point for the listener documentation https://developer.mozilla.org/En/XUL/Method/AddTabsProgressListener Monitoring onStateChange ourselves will possibly provide some clues or a workaround Within facebook we might try something, I found the code for the history manager, could try over-riding it and see if the problem goes away __d("HistoryManager", ["event-extensions", "function-extensions", "Cookie", "Env", "URI", "UserAgent", "copyProperties", "goOrReplace"], function (a, b, c, d, e, f) {return;}); Calling that may or may not do it! For whatever reason facebook seems to be including it twice... found it inside two of their JS files, so calling the function again may over-ride it. I didn't notice anything too suspicious in the manager itself<https://gist.github.com/2837089> . On Wed, May 30, 2012 at 9:29 AM, Anthony Lieuallen <[email protected]>wrote: > Ultimately, we're looking for whatever causes onLocationChange to be > called: > > https://github.com/greasemonkey/greasemonkey/blob/master/content/browser.js#L29 > -- 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.
