Get back to specific alert with updated info about seen/unseen

[damianooldoni]

I am here, let's say:

I want to return to my alert 7, https://alert.riparias.be/alert/7. How to do it?

The only option we have up to now is to use the back arrow of my browser, but in this way the information about seen/unseen is not updated as it is cached.

I see two solutions:

1. do not allow caching so that each time the user wants to go back updated info about See/Unseen is loaded, but I wonder if this is really possible
2. a button, "Back to Alert" so that uesr knows how to return to the specific alert page with updated info without using the browser back arrow.

I discussed it with @niconoe last week, I think. @niconoe: I couldn't find an open issue related to this, sorry. If you can, just delete this or point to the open one.

[niconoe]

Indeed. I plan to implement your suggestion number 2, and I think it's pretty urgent because the current situation is quite impractical for users.

On the longer term, I'm thinking more and more to replace the "occurrence details" page by an occurrence details popup or panel that would open without leaving the alert page (or the main dashboard page). That would solve a lot of similar issues and make the interface better, I think. It's a larger change, so it's not for now. A simple button as you suggest in 2) would already help a lot, I think.

[peterdesmet]

It's probably a bad UX, but how would the application react if the occurrence details were opened in a new tab? Would the application be aware of the change in seen/unseen on the originating page?

[niconoe]

@peterdesmet: no.

There are two interleaved issues, I think:

• The user cannot easily come back to the previous page (especially if you avoid using the back button in modern web apps like I do - but maybe it's just me) => opening in a new tab would help
• The data (read/unread status) is not updated between pages: no easy solution for that

The more I think of it, the more I think we'll really need a single page application for a given data view (either a specific alert or the dashboard at large) if we want a great UI. (all the rest: static pages, alert creation form, login forms, ... can continue as a standard, server-generated HTML pages)

[niconoe]

"Go back button" (either to the alert or tot he website root, according to what lead the user there) is now implemented.

We also need that the "mark the observation as unseen" works the same way.

[niconoe]

@damianooldoni / @peterdesmet : back button implemented and visible on the dev website.

Will now work to make the "mark observation as unseen" follows the same logic.

[damianooldoni]

Back button tested. Nice.

[niconoe]

Also updated the "mark observation as unseen" redirect logic.

Will deploy everything into prod very soon (before my long weekend), if no objections!