| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2023-02-25 | [Glitch] Rename JSX files with proper `.jsx` extension | Renaud Chaput | |
| Port 44a7d87cb1f5df953b6c14c16c59e2e4ead1bcb9 to glitch-soc Signed-off-by: Claire <claire.github-309c@sitedethib.com> | |||
| 2023-02-03 | [Glitch] Run eslint --fix | Claire | |
| I don't like it changing files this way, but it's basically what c49213f0ea311daba590db1d7a14a641cbd9fe93 and a few others did. | |||
| 2019-09-30 | Fix using wrong component in ColumnBackButtonSlim | Thibaut Girka | |
| 2019-09-09 | Use the `Icon` component instead of directly using `i` tag | Thibaut Girka | |
| 2019-04-17 | Shift+click on column Back button to return to last pinable column | Thibaut Girka | |
| 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-03 | Rename themes -> flavours ? ? | kibigo! | |
 |
index : mastodon | |
| Plural Café fork of Mastodon/Glitch Social |
| about summary refs log tree commit diff |