about summary refs log tree commit diff
path: root/config/locales/pt.yml
diff options
context:
space:
mode:
authorThibaut Girka <thib@sitedethib.com>2018-05-23 14:17:05 +0200
committerThibaut Girka <thib@sitedethib.com>2018-05-31 14:39:02 +0200
commitcc396f085d5c706d8d2ddc26af5d551a2d5b9526 (patch)
tree3e3c186d1f3f6915bf60fde5a8ea5c0458557fe5 /config/locales/pt.yml
parentf86d280fd6fb742f836e527efd3f31cf9f9eda0e (diff)
Use history.state to decide whether we should goBack() or go to / (fixes #247)
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.
Diffstat (limited to 'config/locales/pt.yml')
0 files changed, 0 insertions, 0 deletions