sourcebits-robertbiggs
commented
10 years ago Well, the way navigation history is currently handled, there is just one navigation history object for the app. So switching to a different tab will change the navigation of the list in a tab. I just noticed that Apple does preserve a separate navigation history per tab. But I’m not sure how I would go about introducing that. I’m going to have to spend some time thinking about the most efficient way to pull that off and try some prototyping. Sort message, it’s not happing tomorrow. Might be a while even. I’m in the middle of a refactor of how themes work to make it easier to change color schemes.
Robert Biggs Product Director ChocolateChip-UI www.sourcebits.com
On Jul 2, 2014, at 9:47 AM, jeff183 notifications@github.com wrote:
I have 3 tabs in my app. In one tab i have several articles and i use nav and back button to navigate. If the user goes to another tab, i have a button to return to the original tab, same article. I use pub/sub and chui/navigate/leave to know where to return to. I then use $.UIGoToArticle() to attach an event to the button.
So, that works great. But when i return to the original tab and article, it's back history (within that tab) is gone.
Would be nice if that was still there. Not sure if this is an issue or the way it is designed.
— Reply to this email directly or view it on GitHub.
jeff183
I have 3 tabs in my app. In one tab i have several articles and i use nav and back button to navigate. If the user goes to another tab, i have a button to return to the original tab, same article. I use pub/sub and chui/navigate/leave to know where to return to. I then use $.UIGoToArticle() to attach an event to the button.
So, that works great. But when i return to the original tab and article, it's back history (within that tab) is gone.
Would be nice if that was still there. Not sure if this is an issue or the way it is designed.