6 Commits (2a4e44a725db57b8b506de6b09926bd977d4c504)

Author	SHA1	Message	Date
ThibG	b5927301cf	[Glitch] Fix browser notification permission request logic ... Port f54ca3d08e to glitch-soc Signed-off-by: Thibaut Girka <thib@sitedethib.com>	2020-10-21 21:28:47 +02:00
ThibG	2f2b48b227	[Glitch] Fix `/web` redirecting to `/web/web` in web UI ... Port 0f07218e53 to glitch-soc Signed-off-by: Thibaut Girka <thib@sitedethib.com>	2020-02-25 14:30:43 +01:00
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
cwm	72b99f6ee4	bug fix (tootsuite pr #6120)	2017-12-31 08:26:50 -06:00
cwm	0dce26b82b	web push updates (tootsuite PRs #5879, #5941, #6047)	2017-12-30 11:45:01 -06:00
kibigo!	bc4fa6b198	Rename themes -> flavours ? ?	2017-12-03 23:26:40 -08:00