I am glad that you are committed to investigating this thoroughly. I will likely fire up the test environment and see if I can figure out what's going on at some point, although pressing debt demands otherwise. This issue is curious enough to merit attention. Though I imagine I won't get far without digging into Firefox source code considering the limited nature of this problem. I hope we can find at least one other site that reproduces such occurrence!
On Tue, May 29, 2012 at 11:51 PM, Matt Kruse <[email protected]>wrote: > On May 29, 3:46 pm, Anthony Lieuallen <[email protected]> wrote: > > Thanks everyone for your work figuring this out so far. It really should > > be reported as an issue which is tracked until it's fixed: > > I think it needs more investigation... > > > Ideally, with a reproducible testcase which is standalone (not Facebook). > > I'm a bit busy at the moment to do this myself, but if an issue is > > reported, I'll get to it when I have time. > > I tried to create a simplified test case here: > http://socialfixer.com/temp/pushstate.html > > And, the problem does not exhibit itself. So calling pushState by > itself is not enough. There is more going on. I'm going to dig in > further and see if I can figure out exactly what is triggering the GM > script to be re-executed. > > Matt Kruse > > -- > 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. > > -- 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.
