You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Earlier I used to use history.state to decide if an user can go back any further in the application.
But after enabling appcache, it's always null. Is there a workaround or alternate way to know if the user can goback ?
Example use case:
Consider there is a blog app
User clicks a link to a post (I love IronRouter), the link opens in the app.
User then follows this path
I love IronRouter > post author > home > I love IronRouter .
Now when the user goes back, he has to goto home > post author > I lover iron router
At this stage, backbutton won't be displayed.
The text was updated successfully, but these errors were encountered:
Earlier I used to use history.state to decide if an user can go back any further in the application.
But after enabling appcache, it's always null. Is there a workaround or alternate way to know if the user can goback ?
Does it have something to do with hash paths?
#12
Example use case:
Consider there is a blog app
User clicks a link to a post (I love IronRouter), the link opens in the app.
User then follows this path
I love IronRouter > post author > home > I love IronRouter .
Now when the user goes back, he has to goto home > post author > I lover iron router
At this stage, backbutton won't be displayed.
The text was updated successfully, but these errors were encountered: