The issue with the style that you have, is that the templates are nested inside of an ons-page and therefore they are trying to be rendered. I have moved them outside of that tag and everything appears to be working on my end, but I want to make sure it works on your devices.
@munsterlander That was the way to extend animatinos in v1, but unfortunately it won’t work for v2.
@davidfherrerar For Onsen UI 2 right now extending and modifying animators is not an easy task. We still need to make this easier. I’ve made an example with the simple slide animation here.
Basically I made a new animator using simple slide’s pop method in the new push method and changing some minor stuff.
The problem is that the core animators are written in ES6, but here you would need to write ES5 for the browser, and also right now we can only extend the very basic animator, not an already implemented one.
If you really want a pop animation I think right now it would be easier to just delete the pages you don’t need from myNavigator.children HTMLCollection and perform a normal myNavigator.popPage() afterwards.
Anyway, just for the record, this is the code for the custom animator:
@davidfherrerar The “parameter as an option” that you mention is just for the animation and some other information but not for custom data, so in general there is no need to get the parameter back in the new page. You can save data on page’s hide or destroy events and apply it to the new page on init or show events.