Motivation behind the feature and what it will do
Right now, the super unused tab bar only needs to handle one tab and refreshing the page doesn't cause any issues. Once more applications pop up, I think we could cache the what tabs are "open" and have them show up if the page is refreshed or the site is visited again.
Which part of the application will this feature be for?
The tab bar on the main site.
Minimal Viable Product
Code changes
- Updating the
application.ts behaviour to save its state to local storage as a stringified JSON
- When the user open the site,
application.ts will try to read the tab state and restore it if it's possible
- Any invalid applications will be skipped when restoring a session
Motivation behind the feature and what it will do
Right now, the super unused tab bar only needs to handle one tab and refreshing the page doesn't cause any issues. Once more applications pop up, I think we could cache the what tabs are "open" and have them show up if the page is refreshed or the site is visited again.
Which part of the application will this feature be for?
The tab bar on the main site.
Minimal Viable Product
Code changes
application.tsbehaviour to save its state to local storage as a stringified JSONapplication.tswill try to read the tab state and restore it if it's possible