webapp: Allow "open in new tab" (have domains on /domains be <a> links)

Open
#1,192 0 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 14 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Tech stack
html, javascript

Research direction

Start at the webapp entry point that renders the domains list at /domains and inspect how its row click handler navigates to each domain. Done means domain names use native <a> links to their existing destinations, so browser actions such as opening a link in a new tab work.

Written by the indexing model from the issue text.

Description

Hi!

The <tr>s on desec.io/domains currently get a click event, which sends users to /domains/example.com.

Can the domains on the list be links, so open-in-new-tab works?

Currently, because the rows use JavaScript click handlers instead of native elements, users lose the ability to interact with domain links the way they would with any standard hyperlink. This means right-clicking to "Open in New Tab," middle-clicking, or Ctrl/Cmd-clicking all fail to work as expected. For users managing many domains, this is a significant workflow friction, as they often want to open several domains in separate tabs to configure them in parallel without losing their place in the list.

Beyond usability, using semantic links also improves accessibility and aligns with web standards. Screen readers and other assistive technologies can properly identify and announce links, giving users a clear indication that the element is navigable. It also means the browser can show the destination URL on hover in the status bar, giving users confidence about where they're going before they click. Overall, replacing the click handlers with proper anchor elements is a small change that would bring the UI in line with expected browser behavior and make the experience smoother for everyone.

Thanks!

Dominant language
Python
Stars
678
Forks
74
Avg merge
7d 23h
Merged PRs (30d)
1

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from desec-io/desec-stack

All issues in desec-io/desec-stack

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.