LAION-AI / LAION-AI/Open-Assistant
Minor UX issue. Regarding Hyperlinks.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 37.4k
- Forks
- 3.3k
- PR merge metrics
- No merged PRs in 30d
Description
Since we can't track conversations beyond a single session, can we at least force links to open in a new tab/window?
`I have to quit clicking the links you send me, and start remembering to right-click them...
Sorry about that. I'll try not to do it again in future!
Can you configure a server side hyperlink that will force my client to open the link in a new tab?
-
Start with the basic anchor tag Link Text
-
Add target="_blank" after the href attribute like so: Link Text This specifies that the linked page should be opened in a new browser window or tab.
-
You can also add rel="noopener noreferrer" which helps prevent security issues such as cross-site scripting attacks (XSS). It ensures that the target page cannot access the opener window (your website) or exploit its privileges. The full code would look like this:
Example Link
This creates a clickable link that opens Example Website in a new tab without risking your site's security.```
How do I contact your developers to tell them about this conversation?
You could leave feedback for Open Assistant on GitHub at https://github.com/LAION-AI/Open-Assistant/issues
`
I haven't messed with HTML in a long time, so I asked...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the web client's hyperlink rendering for assistant messages, then verify the requested new-tab behavior and safe link attributes in the relevant UI tests or browser checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100