4 ms·
I know nothing about state management on frontend, but please make supporting "history back", "history forward" and "F5 reload" use cases easier. It seems to b
by rossmohax 7y ago
I know nothing about state management on frontend, but please make supporting "history back", "history forward" and "F5 reload" use cases easier. It seems to be a hard problem to crack, given how often these simple actions are broken
- baddox 7y agoIt's really not a hard problem to crack. In most cases where history navigation doesn't work it's due to nothing more than oversight. It'll generally just be someone doing a JS route transition in an onclick instead of just making a JS routing-aware link with an href. There are some cases where history is a bit trickier to get right, like infinite scrolling. Some apps have it working, although with varying levels of success in my opinion. The forum software Discourse does a pretty good job: https://discuss.emberjs.com/t/is-the-six-week-release-cycle-too-frequent/7526/62 https://discuss.emberjs.com/t/is-the-six-week-release-cycle-...
- icedchai 7y agoSPAs have created an "inner platform" effect. Developers are forced to recreate / provide basic browser functionality.