history.back(); doesn't trigger $(document).ready();

Question

I have a webpage that use $(document).ready() to build the interface. Then the user can go to a child page, and to go back to the original page he can press the browser's "previous" button or a "Return" button in the page which triggers a history.back();. Back on the original page, $(document).ready() is not triggered so the page is missing information.

Is there a way to trigger it automatically like if it was a "real load"?

edit

placing an alert in it, the alert is popped but stuff is missing in my interface like if some part of the ready event is missing. Investigating...

edit 2

hahahahaha in document.ready I click some checkbox which are supposed to be unchecked. When I "back" on this page, they are checked so they become unchecked because I reclick them.

Sorry, this is completely my bad :(

What browser are you seeing this in? I recall only Opera having this problem with the back/forward buttons. — Crescent Fresh
– Crescent Fresh, Commented Sep 2, 2010 at 15:27
I'm on Chrome. The user that reported the problem is on Firefox. — Sirber
– Sirber, Commented Sep 2, 2010 at 16:03
Its a Firefox feature, see this post: stackoverflow.com/questions/2638292/… — Kees van Dieren
– Kees van Dieren, Commented Jun 14, 2012 at 10:37

stonyau · Accepted Answer · 2016-04-26 07:30:34Z

29

A quick solution to this problem, use "onpageshow" instead.

window.onpageshow = function(event) { //do something };

answered Apr 26, 2016 at 7:30

stonyau

2,1921 gold badge21 silver badges18 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

Jorge Suárez de Lis Over a year ago

Thanks! None of the other proposed solutions worked properly on both Firefox and Chrome, but this one does.

FredyWenger Over a year ago

Thanks! I have noted, that $(document).ready() not is triggered with history.back(); on mobile browsers (safari and google chrome) under iOS , (whereby it works on desktop.browsers) and have searched a long time... with window.onpageshow it works on all browsers

hanshenrik Over a year ago

warning, pageshow does not fire on iframe elements on firefox 74, but "load" does =/

jave.web Over a year ago

Warning, history back is sorcery! Let's join together and remove its funkyness forever, only thing it should really do is to re-fill previously-filled forms. That's all, otherwise it should load normally x)

Paulo Santos · Accepted Answer · 2010-09-02 15:21:09Z

7

If the user uses the Back button to navigate and you require a full reload of the page, you can set the NO-CACHE policy of the page.

This way the browser is forced to reload the page from the server, even using the Back button.

answered Sep 2, 2010 at 15:21

Paulo Santos

11.7k5 gold badges45 silver badges67 bronze badges

4 Comments

Dutchie432 Over a year ago

Hrmm..nice answer. Hadn't thought of that.

Sirber Over a year ago

I already use: header("Cache-Control: private, no-cache, must-revalidate"); header("Pragma: no-cache");

Sirber Over a year ago

I added <meta http-equiv="pragma" content="no-cache">, but it doesn't reload the page when I press "back".

ajbeaven Over a year ago

Depends on your browser - google chrome doesn't handle it correctly.

BGerrissen · Accepted Answer · 2010-09-02 16:02:43Z

1.) put scripts at the bottom of your page.
2.) execute plugins and whatnot in your last script tag(s).
3.) Do not use onDomReady implementations at all, it's redundant.

People are so accustomed to onload or ondomready, they overlook the fact that putting your scripts at the bottom of a page does virtually the same thing without the need to poll and see if your html is available.

Furthermore, it's also good practise as your scripts do not block html/css rendering either.

Not depending on onDomReady or onLoad implementations solves a lot of issues.

-1, For a browser where onload doesn't work, your solution doesn't work as well. E.g. FireFox, it just doesn't run the script regardless of whether you put it in onload or at the bottom of the page. Did you even test?

Dutchie432 · Accepted Answer · 2010-09-02 15:21:17Z

Very interesting question. You might need to re-trigger the event/function when the page gets focus, or something similar. you might also need to keep a flag variable to track whether an 'event re-triggering' is in order.

Collectives™ on Stack Overflow

history.back(); doesn't trigger $(document).ready();

4 Answers 4

4 Comments

4 Comments

1 Comment

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

4 Comments

4 Comments

1 Comment

Comments

Linked

Related