Add href attribute to links instead of pure javascript for navigation #524

Closed
opened 2026-04-05 16:20:17 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @KoalaG on 3/24/2025

Is your feature request related to a problem? Please describe.
When viewing or making changes to a number of monitors, it is usefull to be able to open each of the monitors in a new tab, and make the changes in each tab at the same time.
Currently, when you click on the name link, or the View Monitor button, these are actioned through the javascript framework, and you are unable to right click > open in new tab (or middle click, or shift+click).

Describe the solution you'd like
Links to monitors (or to any page) should have the href attribute filled so that the user can interact with it like a normal website and allow them to copy the link, or right click to open in new tab.

Describe alternatives you've considered
Have not found an alternative.

Additional context
This is a quality of life enhancement, which would simplify the administration of monitors in oneuptime.

It looks like this would be fixable in Common/UI/Components/Link/Link.tsx by adding href={props.to?.toString()} to the returning element. I'm not familiar enough with the framework to try this and create a PR.

*Originally created by @KoalaG on 3/24/2025* **Is your feature request related to a problem? Please describe.** When viewing or making changes to a number of monitors, it is usefull to be able to open each of the monitors in a new tab, and make the changes in each tab at the same time. Currently, when you click on the name link, or the View Monitor button, these are actioned through the javascript framework, and you are unable to right click > open in new tab (or middle click, or shift+click). **Describe the solution you'd like** Links to monitors (or to any page) should have the href attribute filled so that the user can interact with it like a normal website and allow them to copy the link, or right click to open in new tab. **Describe alternatives you've considered** Have not found an alternative. **Additional context** This is a quality of life enhancement, which would simplify the administration of monitors in oneuptime. It looks like this would be fixable in `Common/UI/Components/Link/Link.tsx` by adding `href={props.to?.toString()}` to the returning element. I'm not familiar enough with the framework to try this and create a PR.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#524