@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…
I’m hitting some (maybe basic) issue. You mentioned before that the the Splitter should be the parent of Navigator for this to work. But then, how can I pass the APP Navigator instance to the Page within the SplitterSide component?
@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.