{"action":"closed","issue":{"url":"https://api.github.com/repos/aurelia/templating-binding/issues/95","repository_url":"https://api.github.com/repos/aurelia/templating-binding","labels_url":"https://api.github.com/repos/aurelia/templating-binding/issues/95/labels{/name}","comments_url":"https://api.github.com/repos/aurelia/templating-binding/issues/95/comments","events_url":"https://api.github.com/repos/aurelia/templating-binding/issues/95/events","html_url":"https://github.com/aurelia/templating-binding/issues/95","id":168223508,"number":95,"title":"should be possible for a view to not be unbound when deactivated","user":{"login":"dkent600","id":1821666,"avatar_url":"https://avatars.githubusercontent.com/u/1821666?v=3","gravatar_id":"","url":"https://api.github.com/users/dkent600","html_url":"https://github.com/dkent600","followers_url":"https://api.github.com/users/dkent600/followers","following_url":"https://api.github.com/users/dkent600/following{/other_user}","gists_url":"https://api.github.com/users/dkent600/gists{/gist_id}","starred_url":"https://api.github.com/users/dkent600/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dkent600/subscriptions","organizations_url":"https://api.github.com/users/dkent600/orgs","repos_url":"https://api.github.com/users/dkent600/repos","events_url":"https://api.github.com/users/dkent600/events{/privacy}","received_events_url":"https://api.github.com/users/dkent600/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-07-29T00:00:36Z","updated_at":"2016-07-29T00:19:19Z","closed_at":"2016-07-29T00:19:19Z","body":"I find, even when assigning the decorator @singleton(false) to the view-model, that while the view-model does then persist as a singleton across activation/deactivation, the bindings and components, etc do not. \r\n\r\n(I assume this is because they are stored in a container that is disposed on deactivation.)\r\n\r\nThe result is that upon every deactivation/activation of a view with a singleton view-model, the view is un-bound and then re-bound. \r\n\r\nIs it possible to cause the bindings to persist across view deactivation/activation?\r\n\r\nDurandal has this functionality.\r\n\r\nAs it stands, switching between views loses potentially a lot of visual state which can be quite a problem for the application user.  I think it is asking a lot of the developer to manually cache every little bit of UI state that is important on every view."}}
{"actor":{"display_login":"EisenbergEffect"}}