[Bug] Wrong content view if logged out and navigating back #1984

New Issue

LucaBernstein · 2022-09-24T22:08:26Z

LucaBernstein commented

2022-09-24 22:08:26 +00:00

Version information:

Frontend Version: 0.19.1
API Version: 0.19.2
Browser and OS Version: Firefox, MacOS

Steps to reproduce:

Open any instance of Vikunja, logged-out. E.g. https://try.vikunja.io/
You will be redirected to /login
Navigate back with browser controls
The login screen will be replaced by a tasks list
...

Expected behavior:

You should stay on the login page / the redirect to /loginshould not be recorded in the SPA history.

Actual behavior:

Login screen is replaced by tasks screen. See screenshot:

Checklist:

I have provided all required information
I am using the latest release or the latest unstable build
I was able to reproduce the bug on try

**Version information:** Frontend Version: 0.19.1 API Version: 0.19.2 Browser and OS Version: Firefox, MacOS **Steps to reproduce:**  1. Open any instance of Vikunja, logged-out. E.g. https://try.vikunja.io/ 2. You will be redirected to `/login` 3. Navigate back with browser controls 4. The login screen will be replaced by a tasks list ... **Expected behavior:**  You should stay on the login page / the redirect to `/login`should not be recorded in the SPA history. **Actual behavior:**  Login screen is replaced by tasks screen. See screenshot: ![image](/attachments/f1da4cbc-c479-4ec2-9d97-370668c8b316) **Checklist:** * [x] I have provided all required information * [x] I am using the latest release or the latest unstable build * [x] I was able to reproduce the bug on [try](https://try.vikunja.io)

image.png

2.3 MiB

konrad added the

kind/bug

label 2022-09-26 12:29:28 +00:00

konrad referenced this issue from a commit

2022-10-05 14:51:39 +00:00

fix: don't try to render auth routes when the user is not authenticated

konrad closed this issue

2022-10-05 14:51:39 +00:00

konrad commented

2022-10-05 14:52:10 +00:00

Fixed in 3af20b6220 - please check with the next unstable build or on try if the problem really went away.

Fixed in https://kolaente.dev/vikunja/frontend/commit/3af20b6220d8fcded9c8c2f0bdef21dc26d748f6 - please check with the next unstable build or on [try](https://try.vikunja.io) if the problem really went away.

konrad referenced this issue from a commit

2024-02-07 14:00:34 +00:00

fix: disabled attribute fallback (#1984)

Sign in to join this conversation.