Feature: Make browser notifications customizable & navigable

[cdprete]

Hello.

As of today, the notification triggered by the UI through the browser API while the status of an instance changes have, somehow, a fixed timeout (5s if I'm not wrong).

In this ticket I would like to request the following feature(s):

• allow to make the timeout configurable, with the option that if it's 0 then the notification(s) should not be automatically dismissed and it's up to the user to dismiss them
• if possible, open the instance details view of the instance the notification refers to when it gets clicked

[codingkiddo]

Hi, I would like to take a look at this.

I’ll first inspect the current browser notification handling in the UI and keep the scope focused on:

• making the auto-dismiss timeout configurable while preserving the current default behavior
• treating 0 as “do not auto-dismiss”
• wiring notification click to the related instance details view if the notification payload has enough instance information

I’ll avoid touching the server-side notifiers unless configuration exposure requires it.

[cdprete]

I’ll avoid touching the server-side notifiers unless configuration exposure requires it.

The server side notifiers are a different kind of notification channel. Indeed they should not be touched.

The configuration, though, must come through the backend like it already happens for other configurations (e.g.: theme colors).

[codingkiddo]

Thanks for clarifying.

Understood — I’ll leave the server-side notifier channels untouched.

I’ll look for the existing backend-to-UI configuration path used for UI settings such as theme colors, add a browser notification timeout setting there with the current behavior preserved as the default, and then consume that value in the frontend browser notification logic.

For the timeout semantics, I’ll treat a positive value as auto-dismiss delay and 0 as “do not auto-dismiss”.