5 Commits (c600bcfe1da3585245112edb596c8cc776959600)

Author	SHA1	Message	Date
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
Thibaut Girka	64d8d0464d	Add show more/less toggle for entire threads in web UI ... Inspired from b6003afcdb but using component properties instead of redux store for hidden/revealed state.	2018-04-22 19:19:01 +02:00
Thibaut Girka	63d671b18f	[Glitch] Fix button hiding when header title is too long ... Port ffb2b8ef8c to glitch-soc	2018-04-22 19:17:10 +02:00
Thibaut Girka	abf7c5b850	[Glitch] Fix column headers accessibility ... Port 08e4c78e78 to glitch-soc. SCSS fix inspired by 69f13e7bca.	2018-04-22 19:17:10 +02:00
kibigo!	bc4fa6b198	Rename themes -> flavours ? ?	2017-12-03 23:26:40 -08:00