| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2020-04-11 | Revert "Revert "Merge branch 'glitch'"" | Starfall | |
| This reverts commit 12d35783db1bb302d7540d8d3690ab6eed3dac3b. | |||
| 2020-03-01 | Revert "Merge branch 'glitch'" | Starfall | |
| Login is broken This reverts commit 22a55edc158352003a3953964c9d332a60c86428, reversing changes made to 5902299384d15249fe4b84b8761d4a49f3c7f6fd. | |||
| 2020-02-25 | [Glitch] Fix `/web` redirecting to `/web/web` in web UI | ThibG | |
| Port 0f07218e53bf581127cdcf5fbf12d9c207ace8d7 to glitch-soc Signed-off-by: Thibaut Girka <thib@sitedethib.com> | |||
| 2018-05-31 | Use history.state to decide whether we should goBack() or go to / (fixes #247) | Thibaut Girka | |
| 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. | |||
| 2017-12-31 | bug fix (tootsuite pr #6120) | cwm | |
| 2017-12-30 | web push updates (tootsuite PRs #5879, #5941, #6047) | cwm | |
| 2017-12-03 | Rename themes -> flavours ? ? | kibigo! | |
 |
index : mastodon | |
| Plural Café fork of Mastodon/Glitch Social |
| about summary refs log tree commit diff |