When you go to the 'create lists' and click back in browser, and then click forward, and then click back, etc - the delete and edit buttons are created for each instance. They don't persist to the backend and on refresh they go away. I thought of the 'transitionTo' but since the browser nav buttons aren't controlled by you you can't attach methods to them(you probably could but..eww) You could certainly 'refresh' the page on back somehow, but doesn't that defeat the purpose of Ember and Ember's data caching to speed things up? I didn't attach any code because it is browser related - the code is all fine. Googling the issue seems to suggest that this is kind of a common problem, but I didn't see any real solutions. I think the problem with hardwiring anything in would be the side effects of 'page jumping' - back and forward in the browser may not follow what I as a developer expect the user to navigate to. Any thoughts on fixes for this?
When you go to the 'create lists' and click back in browser, and then click forward, and then click back, etc - the delete and edit buttons are created for each instance. They don't persist to the backend and on refresh they go away. I thought of the 'transitionTo' but since the browser nav buttons aren't controlled by you you can't attach methods to them(you probably could but..eww) You could certainly 'refresh' the page on back somehow, but doesn't that defeat the purpose of Ember and Ember's data caching to speed things up? I didn't attach any code because it is browser related - the code is all fine. Googling the issue seems to suggest that this is kind of a common problem, but I didn't see any real solutions. I think the problem with hardwiring anything in would be the side effects of 'page jumping' - back and forward in the browser may not follow what I as a developer expect the user to navigate to. Any thoughts on fixes for this?