Our company is building a SPA and we are discussing the best behavior for the browser back button. The SPA is a management tool with many tables and filters. Each time a filter is changed, the URL parameters are updated to reflect the current status.
There are two sides to the argument of what the Back button should do:
- One side thinks that the Back button should change state. Therefore, every time you change a filter, you must push the new state in the browser history.
- The other side thinks the back button should change pages. Therefore, filter changes must be ignored and the browser must return to the previous page / view.
Both options have their advantages and disadvantages. Is there a common opinion about what the Back button should do?