Topics created by mentizm

@mentizm I cannot reproduce this behavior, could you make a simple example in Codepen that we can test?

@Fran-Diox Thank you! Seems to work fine

Hi @mentizm ! You need to use the var attribute of the <ons-navigator> like this: <ons-navigator var="myNavigator"> ... </ons-navigator> By doing this, it is bound as a variable and you can access it with $scope.myNavigator in AngularJS. Here is a simple example on Codepen that illustrates this: http://codepen.io/onsen/pen/yrhtv In the case you are using the Onsen UI 2.0 beta, you also need to include onsenui-angular.js since we’ve split the AngularJS bindings to a separate file. Also, if you are not using AngularJS, the var attribute does not work. Instead you can just select the element and push the page: <ons-navigator id="my-navigator"></ons-navigator> var navigator = document.getElementById('my-navigator') navigator.pushPage('page.html');

Hi I know this is old post but maybe any body had this problem like me when i was upgrading onsenui from 2.1.0 -> 2.2.6 My solution was var readyState = setInterval(function() { if (document && document.readyState === 'complete') { clearInterval(readyState); readyState = null; // Callback main function ons.ready(callback); } }, 10); /Best regards