6 commits

Author	SHA1	Message	Date
ThibG	1b1c7353a8	[Glitch] Fix crash when switching back/from mobile layout ... Port 2673b89971 to glitch-soc Signed-off-by: Thibaut Girka <thib@sitedethib.com>	2019-10-11 22:40:52 +02:00
Eugen Rochko	3134aa0097	[Glitch] Fix scroll to top in single column UI ... Port 293f789239 to glitch-soc Signed-off-by: Thibaut Girka <thib@sitedethib.com>	2019-10-06 00:32:06 +02:00
Thibaut Girka	9b0b130299	Use the Icon component instead of directly using i tag	2019-09-09 19:00:20 +02:00
Thibaut Girka	619d55358f	Shift+click on column Back button to return to last pinable column	2019-04-17 18:40:40 +02:00
Thibaut Girka	37dc96b71b	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
kibigo!	882055afd0	Rename themes -> flavours ? ?	2017-12-03 23:26:40 -08:00

Renamed from app/javascript/themes/glitch/components/column_back_button.js (Browse further)