I think that’s more or less the “contextual action” implemented in my previous post.
Here I fear we perhaps may have a philosophical difference. I endeavor to minimize dependencies amongst actors in my code, because in my experience that tends to be where bugs lie, and I have a harder time documenting, maintaining, and testing code where (for example) a navbar’s template is affected by anything outside navbar-world. I want my navbar’s job to be “telling the world that stuff got clicked”, with nary a care for how other parts of the app might interpret that.
I think that sounds more or less like my contextual action button, except I’m using direct Observables instead of Ionic Events because reasons and death.
I guess basically what I’m saying is that while you might be able to shoehorn this functionality into navigation, it doesn’t feel to me very navigatory, so maybe after all it’s better off separate.
Does that make any sense?