From @NathanaelA on May 21, 2016 23:41

Did you verify this is a real problem by searching

Yes, this is a combination post describing several issues with the current routing system. @valentinstoychev requested I do this and I am linking to any existing issues in the issue tracker. 😀

Tell us about the problem

Current Navigation system has the following issues:

• Inability to cancel a navigate (both forward and back) request via the onNavigatingFrom/onNavigatingTo event handlers see Value accessors using static selectors now. #583, Datepicker ngModel not working only on IOS #618
• Inability to reload the current page without affecting history, see: Expose the native view form the ListViewComponent #243, NativeScript usage of the new HttpClient - causes error? #1087
• Inability to delete a page from the history stack; This needs to be able to happen after loading a page, then I can clear it from the history. backStackVisible is NOT the solution to this, as BSV affects the next page being loaded. If I am on a page and I want to navigate off this page and forget it; I should be able to delete it from the history stack so that it is like the page was never was originally set with BSV. I may not know that page needs to be cleared from the history until they do something on it...
• In ability to add/modify to the history stack, I might want to insert a "Back" page or maybe even completely rewrite the history stack.
• Ability to have TabView/dedicated View (new component required) navigation. This might be impossible with the current design. But Having tabs/view be able to be easily loadable via navigation would improve things, with allowing buttons to remain on bottom but page changes..

Which platform(s) does your issue occur on?

Both

Please provide the following version numbers that your issue occurs with:

2.00

Copied from original issue: NativeScript/NativeScript#2162