Age | Commit message (Collapse) | Author |
|
Port cdb101340a20183a82889f811d9311c370c855e5 to glitch-soc,
but without dropping support for regexp filters yet.
|
|
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.
|
|
|
|
Port cbf97c03bba35a642e6f1d1a698aad7a69ad13a3 to glitch-soc
|
|
Port 9a1a55ce526c956ac6b35897d483c316b7ad4394 to glitch-soc
|
|
Unlike boosts and like, there is no confirmation dialog as misclicking
can be recovered without another user seeing it.
|
|
Port #6628 to glitch-soc flavour
|
|
Port 913a38111ff5b0cb7f412bec93e8314859c88855 to glitch-soc
|
|
|
|
Port 51310125051a75ef7af4e8ffc8b6532c151e96b6 to glitch
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|