@mmike If I was doing what you describe, I would have page B on init calling the function for the data, so that way on pop of C, I can just recall that function. There is no refresh option that you mention that I am aware of. Another option is to use resetToPage(‘b’). This basically pops everything down to A and then reloads B.

@mmike Check this example in Safari and see if it works. That’s a simple init event. Perhaps you are not adding the listeners soon enough in your app? Not sure. For example, event listeners should not be added inside ons.ready because that delays it.

@mmike Not, it cannot have a head element. The important thing here is to register the listener before the actual event is fired. Safari might be running your code later than the other browsers so the init event has already been fired by the time the code is executed (so the listener is added too late). We don’t recommend using <script> tags inside <ons-page> to add event listeners precisely because of this unpredictable behavior of some browsers. Can’t you pass your variables in pushPage(..., { data: { /* custom data */ } }) to that page?