Age | Commit message (Collapse) | Author |
|
Port 5bf100f87be571e86305f3ab244183fc46f1ede2 to glitch-soc
|
|
So far, glitch-soc used history.length to decide whether to call `goBack()` or
go to / in order to not leave the webUI. This made clicking the “Back” button
go to the “Getting started” column instead of going back in the browser's
history when such an action would leave the web UI, but also when:
- The WebUI is refreshed (F5)
- A tab is restored
- The history length reaches its maximum (e.g., 50 in Firefox)
This commit fixes these shortcomings by checking `window.history.state`.
Indeed, we only want to go back in the browser's history when the current
location has been reached from within the WebUI, which only happens via
`pushState` as far as I know. Since browser store the serialized state in
the browser history, this also survives page reload and session restoration.
|
|
Inspired from b6003afcdb1b89eb967a2b211e3b4e26aed9ac9d but using component
properties instead of redux store for hidden/revealed state.
|
|
Port ffb2b8ef8c3c7cd6f57860240378fac8d5964105 to glitch-soc
|
|
Port 08e4c78e78358c2847967e9cc34b4a6497be97e2 to glitch-soc.
SCSS fix inspired by 69f13e7bca90f4855e05a49dd69bba66f843134a.
|
|
|