Weird issues when using site via FireFox

[namida]

Okay, over the last couple of days something weird has been happening when I access the site via the desktop (Windows) version of Firefox. Specifically, sometimes it'll display the wrong page - though the title bar is correct. I noticed this always happens if I go from the main page into a board, then a topic, then try to edit a message. It'll display a different page rather than the edit post page, yet the title will be "Modify Message". (Perhaps strangest of all is that it'll sometimes display the correct page while loading, then switch to the incorrect one after loading completes.)

The same issue doesn't happen when I use a different browser (either IE or Chrome), or when I use the Android version of Firefox. >_> When using Firefox, it *does* also happen on the old forum, so I doubt it's related to this forum specifically.

A forced full refresh seems to load the page correctly (Ctrl+F5), but disabling the cache doesn't make a difference; this still happens.

Anyway, is anyone else having similar issues? If so, does it happen on different browsers, etc?


EDIT: Okay, I haven't extensively tested other browsers, but it's definitely an issue somewhere on my side (not the forum itself) as it just happened on Wikipedia... >_>

[Simon]

I've tried it a couple times, it worked as expected with no problems. The URL is what it should be, too. Ancient Firefox version on Linux.

Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20121207 Iceweasel/3.5.16 (like Firefox/3.5.16). Javascript enabled

-- Simon

[namida]

I completely wiped Firefox from my hard drive and reinstalled it, and it seemed fixed, until I logged into my Sync account again. After that, the errors came back. I've now done the same again but without re-syncing it and seems so far so good. So, it'd appear that some obscure setting got messed up or something...

EDIT: Or not, now it's doing it again...

EDIT: Seems I've found the culprit. It's the Linkification extension... I don't know why it would be doing this, but when I disable it, I no longer have this issue.