Weird forward/back problem

Since the last week, maybe two weeks, I've been noticing some odd behaviour on the Back and Forward buttons when using Opera 10.10. I need to press them twice to be 'effective'.

If I look carefully, I notice that after initially loading the page (which completes as evidenced by the loading indicator disappearing), it ninja-loads the same page again, or so I assume. The loading indicator will appear again for a tiny little moment.

This is further evidenced if I look at my back-button history right now: it shows the Administration page listed twice (prior to that, I only opened the main page here.)

I can't really test this on other browsers (IE is the crappiest piece of software ever on W7 x64, and I have nothing else installed), but the Gammon forums are the only place in which this behaviour has ever happened, thus I think it is a recent change here that causes it. As I said, it is quite recent.

I'd appreciate it if this could be fixed, since it is bloody annoying. I thought for a while my opera was bugged when the back button got all temperamental on me. :D

Edit: Oh, and when actually going back a page, it immediately reloads again, thus wiping my Forward history as well. As I said, quite bloody annoying this. :)

I don't have this issue on Chrome, Firefox 3.5.7, or IE8. Perhaps it's the Google Translate script that I think Nick recently added? Try disabling Javascript and see if it still occurs.

I installed Opera and can reproduce the problem, however only on Opera it seems.

I suspect Twisol is right - when you select a language under Google Translate the page indeed reloads (translated), but under Opera it looks like it does it anyway.

Bah, annoying. I'm not turning my JS off permanently, though. This is the first Javascript related problem I've had in ages with Opera, and I refuse to add kludges and crap. Hopefully Google will fix it soon. :/

Edit: I fixed it by blocking the URL of the external Javascript. Everything works wonders again now, thanks for pointing out the source of the problem. :)

Do you use the translations? Do you translate into Dutch for example? Maybe an option for forum users to suppress the translation option.

Nope I don't translate at all. And when I tried it, selecting Afrikaans (was at the top of the list) didn't do boopkiss.

I think it is totally broken on Opera currently. Or I am jinxed.

(Not that they'd care either way, Google Translate is probably still in beta!)

Plain Google Translate works fine for me though, it's just your javascript thingymajiggy.

Google's recommended javascript.

Namely:


<div id="google_translate_element"></div>
<script>
function googleTranslateElementInit() {
new google.translate.TranslateElement({
pageLanguage: 'en'
}, 'google_translate_element');
}
</script>
<script
src="http://translate.google.com/translate_a/element.js?cb=googleTranslateElementInit">
</script>


In fact that failed the W3C validator, so I amended it to:


<div id="google_translate_element"></div>
<script type="text/javascript">
function googleTranslateElementInit() {
new google.translate.TranslateElement({
pageLanguage: 'en'
}, 'google_translate_element');
}
</script>
<script type="text/javascript"
src="http://translate.google.com/translate_a/element.js?cb=googleTranslateElementInit">
</script>


That passed the validator, but still has the problem in Opera.

I don't think such an option is necessary, Nick. If Opera users, and maybe other exotic animals, stumble upon these issues, they can just add "http://translate.google.com/translate_a/element.js?*" to their blocked content list. (Right-click, Block Content..., Details..., Add, etc.)

It should block all the relevant translate stuff from being loaded. And when it gets fixed, we can easily remove it again. But if we remove it, we likely don't need it in the first place, so either way, it's only a loss for people who aren't using it right now. :)

Well that seemed to work. :)

You found your own solution, well done!