Thibaut Girka cc396f085d 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.		2018-05-31 14:39:02 +02:00
..
components	[Glitch] Allow clients to fetch statuses made while they were offline	2018-05-29 21:25:28 +02:00
containers	[Glitch] Do not crash in getStatusIds when there is a gap in the timeline	2018-05-29 21:25:28 +02:00
index.js	Use history.state to decide whether we should goBack() or go to / (fixes #247)	2018-05-31 14:39:02 +02:00