@kk Hi! That’s weird, the code seems fine. Can you try replacing the content of ons-splitter-side with normal div tags and see if the onclick is triggered? Didn’t have the chance to test iOS 11 myself yet…
There are several things that do not seem OK with this component:
-> Where do we get back the options.data passes as second parameter of the pushPage method?
-> there should be all core ons-navigator component methods available on Navigator like: insertPage(index, page, [options]), removePage(index, [options]), resetToPage(page, [options]), bringPageTop(item, [options])…
@Piotr-Mitoraj For the next time I’d recommend you to try things in our tutorial app and then export it to Codepen (there is a button to do it automatically). This way you will always use the latest version. And I think the interface is handy
@meisam3322 The same way you have a global splitter you can have a global tabbar. But you need to choose the component hierarchy yourself. This example combines the three components. It’s probably different to what you need, but it may help you to clarify.
These components are just “frames” with a changeable content. You are nesting different frames and you just need to be aware of which frame’s content you should change and which not. In other words, if you change the content of the very first component, the other components will be gone.