{"action":"opened","issue":{"url":"https://api.github.com/repos/winjs/winjs/issues/920","labels_url":"https://api.github.com/repos/winjs/winjs/issues/920/labels{/name}","comments_url":"https://api.github.com/repos/winjs/winjs/issues/920/comments","events_url":"https://api.github.com/repos/winjs/winjs/issues/920/events","html_url":"https://github.com/winjs/winjs/issues/920","id":56808621,"number":920,"title":"Q: Best way to handle back-navigation parameters?","user":{"login":"omnoms","id":7261863,"avatar_url":"https://avatars.githubusercontent.com/u/7261863?v=3","gravatar_id":"","url":"https://api.github.com/users/omnoms","html_url":"https://github.com/omnoms","followers_url":"https://api.github.com/users/omnoms/followers","following_url":"https://api.github.com/users/omnoms/following{/other_user}","gists_url":"https://api.github.com/users/omnoms/gists{/gist_id}","starred_url":"https://api.github.com/users/omnoms/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/omnoms/subscriptions","organizations_url":"https://api.github.com/users/omnoms/orgs","repos_url":"https://api.github.com/users/omnoms/repos","events_url":"https://api.github.com/users/omnoms/events{/privacy}","received_events_url":"https://api.github.com/users/omnoms/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-02-06T12:56:40Z","updated_at":"2015-02-06T12:56:40Z","closed_at":null,"body":"I've now built a whole view/page that I would like to use like a controller.. basically when a user has selected items in a SeZo-calendar, I want to return those to the previous view when the back() navigation occurs from that page.\r\n\r\nWhat's best practice here? I could just create a globally scoped namespace that holds the calendar values (which I am doing now), but is that really the only way? Can I capture when a user has returned to a view by navigating backwards?\r\n\r\nI'm thinking in terms of separation of concerns that the calendar page shouldn't hold logic depending on which view it was navigated to but rather be dumb and just return a value in the back-navigation event..."}}