Firefox Issue Try Again Button on Bottom of Page

Dorsum-button stops working

Hello experts.

I have a curious problem where the back-push stops working - and other threads regarding this issue has proven unsuccessful in my case, similar changing the browser.backspace_action value, resetting Firefox and disable hardware acceleration.

Alright, try this link: http://htmlticker.nmd.dk/udenadform/index.php?page=1 When clicking the number buttons, the page changes - and when clicking the back-button, it returns to the previous pages. So far, so good.

Now, endeavour this: http://htmlticker.nmd.dk/medadform/alphabetize.php?page=1 Try clicking some numbers, for instance one to v and click back. Nothing happens, right? The folio reloads, but the browser doesn't return to the previous page.

The difference betwixt the ii pages are that the upper link's sourcecode points directly to the ticker HTML, while the lower link's sourcecode points through Adform advertizement engine - but still, it should rewind as usual.

Any vivid ideas are much appreciated - at to the lowest degree a reason, and then I tin can inform our customer.

Hello experts. I have a curious problem where the back-button stops working - and other threads regarding this result has proven unsuccessful in my instance, like changing the browser.backspace_action value, resetting Firefox and disable hardware dispatch. Alright, try this link: http://htmlticker.nmd.dk/udenadform/alphabetize.php?page=one When clicking the number buttons, the page changes - and when clicking the back-push button, it returns to the previous pages. Then far, then good. Now, try this: http://htmlticker.nmd.dk/medadform/index.php?folio=ane Attempt clicking some numbers, for instance ane to 5 and click dorsum. Nix happens, right? The page reloads, but the browser doesn't return to the previous page. The difference between the two pages are that the upper link's sourcecode points direct to the ticker HTML, while the lower link's sourcecode points through Adform advertizing engine - but still, it should rewind every bit usual. Any bright ideas are much appreciated - at to the lowest degree a reason, then I tin can inform our customer.

Chosen solution

Hi, to understand this trouble it's of import to keep in listen what the Dorsum button is supposed to do (even though it may seem obvious :-)). Back essentially ways "revert the terminal navigation action that took identify on this page". On pages that use frames/iframes, the browser must have care to ensure Back only affects the frame that was navigated almost recently - or information technology will in most cases fail to work as the user expects.

What I believe (based on like cases I've analysed) is happening here, is that some JavaScript on this page navigates an IFRAME in a way Firefox registers as a "reversible" navigation. A unmarried click on the back button volition thus opposite the navigation in the (possibly invisible) IFRAME and the user will believe null happened. Double-clicking the dorsum button will often successfully go back when yous are in this state.

If it works in other browsers, it means Firefox is using slightly different logic to register what navigations are "reversible" - and I would personally consider that a issues in Firefox, though it'southward entirely possible that we would suspension dorsum functionality on another site trying to set up this. -Hallvord

Read this reply in context 👍 1

All Replies (20)

Sometimes a problem with Firefox may be a issue of malware installed on your reckoner, that y'all may not be aware of.

You lot tin can endeavour these complimentary programs to browse for malware, which work with your existing antivirus software:

• Microsoft Safety Scanner
• MalwareBytes' Anti-Malware
• TDSSKiller - AntiRootkit Utility
• Hitman Pro
• ESET Online Scanner

Microsoft Security Essentials is a good permanent antivirus for Windows seven/Vista/XP if yous don't already accept i.

Further information tin can be found in the Troubleshoot Firefox issues caused by malware article.

Did this fix your problems? Please written report dorsum soon.

Sometimes a problem with Firefox may be a upshot of malware installed on your computer, that you lot may non be aware of. You can try these free programs to browse for malware, which work with your existing antivirus software: * [http://www.microsoft.com/security/scanner/default.aspx Microsoft Safety Scanner] * [http://www.malwarebytes.org/products/malwarebytes_free/ MalwareBytes' Anti-Malware] * [http://support.kaspersky.com/faq/?qid=208283363 TDSSKiller - AntiRootkit Utility] * [http://www.surfright.nl/en/hitmanpro/ Hitman Pro] * [http://www.eset.com/the states/online-scanner/ ESET Online Scanner] [http://windows.microsoft.com/MSE Microsoft Security Essentials] is a good permanent antivirus for Windows 7/Vista/XP if you lot don't already have one. Farther data tin be constitute in the [[Troubleshoot Firefox issues acquired past malware]] article. Did this fix your problems? Delight report back before long.

Well, I'm using total licensed versions of the newest Spyhunter and AVG Internet Security and none has been found. Likewise, this error was reported to u.s.a. by our clients, who got the information from several visitors on the websites, running the ticker, and so I think the reason is located somewhere else.

But practice you meet the problem too on the lower link?

Well, I'm using full licensed versions of the newest Spyhunter and AVG Cyberspace Security and none has been found. Likewise, this error was reported to us by our clients, who got the information from several visitors on the websites, running the ticker, so I think the reason is located somewhere else. But do '''y'all ''' see the problem equally well on the lower link?

I have tried the above sites and both work correctly.
Delight attempt this on Internet Explorer or another browser if possible. (Non Google Chrome)

Do non use Google Chrome because it has many congenital in plugins. This prevents y'all from diagnosing any software issues.

I accept tried the above sites and both work correctly.<br> Delight try this on Net Explorer or another browser if possible. (Non Google Chrome) Practice non utilize Google Chrome because it has many congenital in plugins. This prevents you from diagnosing whatsoever software issues.

It works perfectly in Internet Explorer. Even so, I just made an observation. Please see the attached screendump from Charles.

What I did was to step through the numbers from i to vii so click back, three times (marked in blue). As you can run across, information technology doesn't reload the previous index.php-file, just still loads the jquery-file.

It works like this: The index.php-file calls the adserving service, which reads the HTML-imprint (chosen 841x26.html and a nocache, which refreshes every minute). 841x26.html uses jquery.webticker.js

Information technology works perfectly in Internet Explorer. However, I simply made an observation. Please see the attached screendump from Charles. What I did was to footstep through the numbers from 1 to vii and and so click back, three times (marked in blue). As you can see, it doesn't reload the previous index.php-file, but still loads the jquery-file. It works similar this: The index.php-file calls the adserving service, which reads the HTML-banner (called 841x26.html and a nocache, which refreshes every minute). 841x26.html uses jquery.webticker.js

Modified Oct 22, 2013 at ii:37:44 PM PDT by hertugen

This sounds like an incompatibility with Firefox, just I'chiliad not sure.

I'll speak with the support team and written report dorsum soon.

This sounds like an incompatibility with Firefox, only I'grand not sure. I'll speak with the support squad and report dorsum soon.

Hello hertugen,

I wasn't able to encounter the issue that you lot're reporting on a Windows 7 machine running FF24. Do you accept any addons installed which might be causing these bug? Try Firefox Condom Manner to encounter if the problem goes away. Safe Manner is a troubleshooting way, which disables most add together-ons.

(If yous're not using it, switch to the Default theme.)

• On Windows you tin open up Firefox iv.0+ in Safe Way past holding the Shift key when you open up the Firefox desktop or Outset menu shortcut.
• On Mac y'all tin can open Firefox iv.0+ in Condom Mode past property the option key while starting Firefox.
• On Linux you tin can open Firefox four.0+ in Safe Style by quitting Firefox and then going to your Final and running: firefox -prophylactic-mode (you lot may need to specify the Firefox installation path e.g. /usr/lib/firefox)
• Or open the Help menu and click on the Restart with Add together-ons Disabled... menu detail while Firefox is running.

Once you get the pop-up, just select "'Start in Prophylactic Mode"

If the issue is not nowadays in Firefox Prophylactic Fashion , your trouble is probably caused by an extension, and you need to figure out which one. Please follow the Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems article for that.

To exit the Firefox Safe Mode, just close Firefox and wait a few seconds before opening Firefox for normal use once again.

When y'all figure out what'due south causing your issues, please allow us know. It might assistance other users who accept the same problem.

Give thanks you.

Hullo hertugen, I wasn't able to encounter the issue that you're reporting on a Windows 7 machine running FF24. Do you have any addons installed which might be causing these issues? '''Endeavor Firefox Safe Style''' to see if the problem goes away. Safe Mode is a troubleshooting fashion, which disables most add-ons. ''(If you're non using it, switch to the Default theme.)'' * On Windows yous tin open Firefox iv.0+ in Prophylactic Way past holding the '''Shift''' key when yous open the Firefox desktop or Start menu shortcut. * On Mac yous can open up Firefox 4.0+ in Safe Mode past belongings the '''choice''' fundamental while starting Firefox. * On Linux yous can open up Firefox 4.0+ in Safe Manner by quitting Firefox then going to your Terminal and running: firefox -safe-mode (you lot may demand to specify the Firefox installation path east.chiliad. /usr/lib/firefox) * Or open the Assist bill of fare and click on the '''Restart with Add-ons Disabled...''' menu particular while Firefox is running. [[Image:FirefoxSafeMode|width=520]] ''Once you lot get the pop-up, only select "'Starting time in Safe Mode"'' [[Image:Safe Mode Fx 15 - Win]] '''''If the outcome is not present in Firefox Condom Mode''''', your problem is probably caused by an extension, and y'all need to effigy out which one. Please follow the [[Troubleshooting extensions and themes]] article for that. ''To leave the Firefox Safe Fashion, just close Firefox and wait a few seconds before opening Firefox for normal use over again.'' ''When yous figure out what's causing your issues, delight let u.s.a. know. Information technology might help other users who have the same problem.'' Thank you.

Hello and cheers for your reply. I'm sorry, but it didn't make much of a departure. At beginning glance, it may appear to work - just if you go through the row of numbers a couple of times, you should run into the same thing in this version. The problem is most credible if the page has been buried, so please endeavour to go through the numbers a couple of times.

http://screencast.com/t/3KqrGqnbGq9 - a screengrab of the trouble

- I opened the browser, cleared the cache, restarted Firefox and opened the page. As the video shows, the problem persists.

Now, the reason why this is and then important in this case is that the ticker is running at multiple places at, for instance, world wide web.bold.dk. The users navigate effectually a chip and is suddenly "imprisoned" to the same folio.

Hello and thank you lot for your answer. I'one thousand deplorable, just it didn't make much of a difference. At get-go glance, it may appear to piece of work - but if yous go through the row of numbers a couple of times, yous should encounter the same thing in this version. The problem is most apparent if the page has been cached, so delight try to go through the numbers a couple of times. http://screencast.com/t/3KqrGqnbGq9 - a screengrab of the problem - I opened the browser, cleared the enshroud, restarted Firefox and opened the folio. As the video shows, the problem persists. Now, the reason why this is so important in this case is that the ticker is running at multiple places at, for instance, www.bold.dk. The users navigate around a bit and is suddenly "imprisoned" to the same page.

Chosen Solution

Hi, to empathise this problem it'southward important to continue in mind what the Dorsum button is supposed to practise (fifty-fifty though it may seem obvious :-)). Dorsum substantially means "revert the terminal navigation activeness that took identify on this page". On pages that utilize frames/iframes, the browser must take care to ensure Back only affects the frame that was navigated most recently - or it volition in most cases fail to work as the user expects.

What I believe (based on similar cases I've analysed) is happening here, is that some JavaScript on this page navigates an IFRAME in a way Firefox registers as a "reversible" navigation. A single click on the dorsum button will thus reverse the navigation in the (perhaps invisible) IFRAME and the user will believe aught happened. Double-clicking the back push will often successfully become back when yous are in this state.

If it works in other browsers, it ways Firefox is using slightly dissimilar logic to register what navigations are "reversible" - and I would personally consider that a bug in Firefox, though it's entirely possible that we would pause back functionality on some other site trying to set up this. -Hallvord

Hi, to understand this problem it'due south important to go along in mind what the Dorsum push is supposed to do (even though it may seem obvious :-)). Back substantially means "revert the concluding navigation action that took identify on this page". On pages that use frames/iframes, the browser must accept care to ensure Dorsum only affects the frame that was navigated virtually recently - or it volition in near cases neglect to work as the user expects. What I believe (based on similar cases I've analysed) is happening hither, is that some JavaScript on this page navigates an IFRAME in a way Firefox registers every bit a "reversible" navigation. A unmarried click on the dorsum push button will thus reverse the navigation in the (maybe invisible) IFRAME and the user will believe nothing happened. Double-clicking the dorsum push button will often successfully become back when you are in this land. If it works in other browsers, information technology means Firefox is using slightly unlike logic to register what navigations are "reversible" - and I would personally consider that a issues in Firefox, though it'south entirely possible that we would interruption back functionality on some other site trying to fix this. -Hallvord

Seems to be working here.

Which entries practise you run into if you correct-click the Back button on the Navigation Toolbar?

---

Offset Firefox in Safety Manner to bank check if i of the extensions (Firefox/Firefox/Tools > Add together-ons > Extensions) or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Firefox/Tools > Add-ons > Appearance).

• Practise NOT click the Reset button on the Safe Mode start window.

• https://support.mozilla.org/kb/Safe+Mode
• https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes

Seems to be working here. Which entries practise you lot encounter if you right-click the Back button on the Navigation Toolbar? ----- Start Firefox in <u>[[Prophylactic Mode|Safe Mode]]</u> to bank check if 1 of the extensions (Firefox/Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Firefox/Tools > Add together-ons > Appearance). *Do NOT click the Reset push on the Safe Mode starting time window. *https://back up.mozilla.org/kb/Safety+Fashion *https://back up.mozilla.org/kb/Troubleshooting+extensions+and+themes

Howdy contributors.

Now, it is working perfectly. I had a jQuery part (which sets the background color in a DIV). This code was run in the header AND in the body onLoad and this - for some reason - caused the dorsum-logic to malfunction at some point as shown in the screen capture video.

I accept deleted the call in the header and modified the PHP-function a flake - and everything works as intended.

My gratitude to everybody, specially Hallvord and our customer's IT-dept, who brought me on the right track :-)

Hello contributors. Now, it is working perfectly. I had a jQuery part (which sets the background color in a DIV). This code was run in the header AND in the body onLoad and this - for some reason - caused the back-logic to malfunction at some point as shown in the screen capture video. I have deleted the call in the header and modified the PHP-role a bit - and everything works equally intended. My gratitude to everybody, peculiarly Hallvord and our client's IT-dept, who brought me on the right track :-)

Interesting. How exactly did it prepare groundwork color? Did it use certificate.write()? I'm request considering document.write() after loading is finished volition create (i.e. navigate to) a new document. This has implications for how the back button works.

Interesting. How exactly did it gear up groundwork colour? Did it employ document.write()? I'one thousand asking considering document.write() after loading is finished will create (i.due east. navigate to) a new document. This has implications for how the dorsum button works.

You can see for yourself in the javascript sourcecode: http://htmlticker.nmd.dk/841x26/webticker.php - the second background (and redundant) initialization has been removed from <head> and consisted of the line <script ="javascript">justerTema(0)</script>

It was a mistake to fifty-fifty have the code located there - but I constitute it curious that it had then much influence over the navigation buttons as demonstrated. Lesson learned.

You can meet for yourself in the javascript sourcecode: http://htmlticker.nmd.dk/841x26/webticker.php - the second groundwork (and redundant) initialization has been removed from <head> and consisted of the line <script ="javascript">justerTema(0)</script> It was a mistake to even have the lawmaking located there - merely I found information technology curious that information technology had so much influence over the navigation buttons every bit demonstrated. Lesson learned.

Whoa - that code only sets certificate.torso.manner.backgroundColor - there is absolutely no reason that should interfere with the dorsum push. If that did actually happen information technology'due south a bug, and should be reported! Are you able to recreate the problem with as footling code as possible?

Whoa - that lawmaking just sets document.body.style.backgroundColor - there is admittedly no reason that should interfere with the dorsum button. If that did actually happen information technology's a problems, and should be reported! Are you able to recreate the problem with equally little code as possible?

Hello everybody. Just for your information; I'll provide additional information in club to shed some lights over things - I just take to become an overview myself, since our customer has provided me with three solutions where one works and two doesn't, using three different methods.

I'll try to see if there's whatever logic in those occurrences and get back every bit soon as possible, so that this thread tin be closed, once and for all.

Hello everybody. Just for your data; I'll provide additional data in order to shed some lights over things - I but have to get an overview myself, since our client has provided me with three solutions where ane works and two doesn't, using three different methods. I'll effort to meet if there'southward any logic in those occurrences and get back as soon as possible, so that this thread can exist closed, in one case and for all.

Had similar problem with dorsum push. Intermittently dorsum page would not load. I disabled a colour theme (furfox tail twister) and it resolved my problem.

Had similar trouble with back button. Intermittently dorsum page would non load. I disabled a color theme (furfox tail twister) and it resolved my problem.

Modified Dec 3, 2013 at four:22:23 PM PST by piccirilli

Annotation that you tin agree downwards the left mouse button on the Back button to open up the tab history list.

Note that you tin can hold downward the left mouse push button on the Back button to open the tab history list.

Yeah, just that is a hassle for quick browsing.

Yeah, just that is a hassle for quick browsing.

I am having this same trouble, but have narrowed the trouble downwardly to Cloudflare integration.

I use Cloudflare to speed upward my site loading times. For some reason, information technology loads the site in "pieces" with a short pause in betwixt each piece. This apparently causes Firefox to think that each piece is a reversible navigation.

And so on my site, TillHeComes.org to actually become "Back" from any post or page, you commonly have to printing the "Back" push button three times earlier it actually goes back.

I have submitted a ticket to Cloudflare every bit well, just recall that since my site works fine with Chrome, IE, and Safari, it might be a bug with the FF browsing logic, as stated in i of the other comments in a higher place.

I am having this same problem, but accept narrowed the problem down to Cloudflare integration. I employ Cloudflare to speed upward my site loading times. For some reason, it loads the site in "pieces" with a short intermission in between each piece. This apparently causes Firefox to think that each piece is a reversible navigation. Then on my site, [http://world wide web.tillhecomes.org TillHeComes.org] to actually go "Dorsum" from any post or folio, you usually have to press the "Back" button iii times before it actually goes back. I accept submitted a ticket to Cloudflare as well, but think that since my site works fine with Chrome, IE, and Safari, it might exist a bug with the FF browsing logic, as stated in i of the other comments in a higher place.

I think this is (or is related to) https://bugzilla.mozilla.org/show_bug.cgi?id=148794 - but information technology's a very former bug, and equally you can encounter from the history and comments a solution was attempted and then backed out. Frankly, how the back button should work isn't ever well understood or specified. I've written a exam case - code here: https://gist.github.com/hallvors/7928615 - which shows that IE does the same thing equally Firefox, while Chrome and Opera (Presto) hold on not saving history entries for document.write(). I'm pretty sure Opera changed this a couple of years ago.

BTW, have you changed your page to avoid this problem? I could no longer reproduce - which is a bit of a pity, because I wanted to bank check if information technology'southward also a problem in Internet Explorer. Per my test case it should be ;-)

I remember this is (or is related to) https://bugzilla.mozilla.org/show_bug.cgi?id=148794 - simply it'due south a very sometime problems, and equally yous tin meet from the history and comments a solution was attempted and so backed out. Frankly, how the back button should work isn't ever well understood or specified. I've written a test case - lawmaking here: https://gist.github.com/hallvors/7928615 - which shows that IE does the aforementioned affair equally Firefox, while Chrome and Opera (Presto) concord on not saving history entries for document.write(). I'm pretty sure Opera changed this a couple of years ago. BTW, have y'all changed your page to avoid this trouble? I could no longer reproduce - which is a chip of a pity, because I wanted to bank check if it'southward likewise a trouble in Internet Explorer. Per my exam instance information technology should exist ;-)

(And since yous said information technology isn't a problem in IE, I'd similar to expect into how Cloudflare avoids running into this same outcome - it seems likely that they work around it for IE but haven't washed the same workaround for Firefox..)

(And since you said it isn't a trouble in IE, I'd like to look into how Cloudflare avoids running into this aforementioned issue - it seems probable that they work effectually it for IE but oasis't washed the same workaround for Firefox..)

mosspromento.blogspot.com

Source: https://support.mozilla.org/en-US/questions/975037

Share this post