On Thu, Mar 27, 2014 at 12:18 PM, Prateek Jadhwani <[email protected]> wrote: > I will try popState api this weekend to test out this theory. Well, if we > are using Routers in the app, then it should be fairly easy to drop the > user to the previous state. The question is what should be use to store data > that cannot be risked stored in URL, like oAuth key.
The system/platform changes would likely need to be made to make pushState a viable option. (I'll use that instead of popstate, as popstate is just the event, where pushState is the setting up of data). At least, for the use cases I think that triggered this thread: when the app gets shut down because of memory constraints. If it was a solid option, then pushState allows storing a state object that is not reflected in the URL[1]. That said, for something like an oAuth token, you may want to store more persistently in localStorage or IndexedDB, if you want it to survive more than just the one oAuth consumer interaction. [1] https://developer.mozilla.org/en-US/docs/Web/Guide/API/DOM/Manipulating_the_browser_history _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
