[PR #21723] [MERGED] feat: update admin users and evaluations sidebars to leverage native anchor tags for robust new-tab link capabilities #81114

New Issue

2026-05-13T15:27:24-05:00

GiteaMirror commented

2026-05-13 15:27:24 -05:00

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/21723
Author: @silentoplayz
Created: 2/22/2026
Status: ✅ Merged
Merged: 2/23/2026
Merged by: @tjbck

Base: dev ← Head: fix/admin-users-evaluations-new-tab

📝 Commits (1)

962b780 feat(ui): update admin users and evaluations sidebars to leverage native anchor tags for robust new-tab link capabilities

📊 Changes

2 files changed (+20 additions, -24 deletions)

View changed files

📝 src/lib/components/admin/Evaluations.svelte (+10 -12)
📝 src/lib/components/admin/Users.svelte (+10 -12)

📄 Description

Pull Request Checklist

Note to first-time contributors: Please open a discussion post in Discussions to discuss your idea/fix with the community before creating a pull request, and describe your changes before submitting a pull request.

This is to ensure large feature PRs are discussed with the community first, before starting work on it. If the community does not want this feature or it is not relevant for Open WebUI as a project, it can be identified in the discussion before working on the feature and submitting the PR.

Before submitting, make sure you've checked the following:

Target branch: Verify that the pull request targets the dev branch. PRs targeting main will be immediately closed.
Description: Provide a concise description of the changes made in this pull request down below.
Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
Documentation: Add docs in Open WebUI Docs Repository. Document user-facing behavior, environment variables, public APIs/interfaces, or deployment steps.
Dependencies: Are there any new or upgraded dependencies? If so, explain why, update the changelog/docs, and include any compatibility notes. Actually run the code/function that uses updated library to ensure it doesn't crash.
Testing: Perform manual tests to verify the implemented fix/feature works as intended AND does not break any other functionality. Include reproducible steps to demonstrate the issue before the fix. Test edge cases (URL encoding, HTML entities, types). Take this as an opportunity to make screenshots of the feature/fix and include them in the PR description.
Agentic AI Code: Confirm this Pull Request is not written by any AI Agent or has at least gone through additional human review AND manual testing. If any AI Agent is the co-author of this PR, it may lead to immediate closure of the PR.
Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
Design & Architecture: Prefer smart defaults over adding new settings; use local state for ephemeral UI logic. Open a Discussion for major architectural or UX changes.
Git Hygiene: Keep PRs atomic (one logical change). Clean up commits and rebase on dev to ensure no unrelated commits (e.g. from main) are included. Push updates to the existing PR branch instead of closing and reopening.
Title Prefix: To clearly categorize this pull request, prefix the pull request title using one of the following:
- feat: New feature

Changelog Entry

Description

Upgraded the Users and Evaluations sidebar navigation components inside the Administration panel to inherently support native browser new-tab actions securely (such as middle-clicking to open in a background tab natively).

Added

Inserted standard component <a href...> navigation mappings correctly tracking evaluations and users route tabs internally across both elements precisely targeting their respective endpoints.
Preserved drag safeguards seamlessly mapping draggable="false" accompanied by class="... select-none" identical to previous iteration templates across the rest of the Admin routes natively.

Changed

Converted <button> components driving Single-Page-Application routing exclusively via goto(route) interactions into robust HTML5 native anchors identically structured identically parsing inside src/lib/components/admin/Evaluations.svelte and src/lib/components/admin/Users.svelte.

Removed

Redundant pure UI button overrides previously suppressing local native HTML capabilities.

Additional Information

Context: Just like the admin/Settings.svelte navigation pane addressed earlier, the sub-tabs governing the Users view (Overview vs Groups) and Evaluations views (Leaderboard vs Feedback) were rendering inside on:click bound <button> nodes blocking normal interaction commands via mouse. Adjusting them to natively route through <a href...> standard elements explicitly allows native mechanisms uninterrupted.
Related PR: https://github.com/open-webui/open-webui/pull/21721

Screenshots or Videos

Before

After

Contributor License Agreement

By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.

Note

Deleting the CLA section will lead to immediate closure of your PR and it will not be merged in.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/21723 **Author:** [@silentoplayz](https://github.com/silentoplayz) **Created:** 2/22/2026 **Status:** ✅ Merged **Merged:** 2/23/2026 **Merged by:** [@tjbck](https://github.com/tjbck) **Base:** `dev` ← **Head:** `fix/admin-users-evaluations-new-tab` --- ### 📝 Commits (1) - [`962b780`](https://github.com/open-webui/open-webui/commit/962b780cc6e3eca3459f946015cd05963627ea52) feat(ui): update admin users and evaluations sidebars to leverage native anchor tags for robust new-tab link capabilities ### 📊 Changes **2 files changed** (+20 additions, -24 deletions) <details> <summary>View changed files</summary> 📝 `src/lib/components/admin/Evaluations.svelte` (+10 -12) 📝 `src/lib/components/admin/Users.svelte` (+10 -12) </details> ### 📄 Description  # Pull Request Checklist ### Note to first-time contributors: Please open a discussion post in [Discussions](https://github.com/open-webui/open-webui/discussions) to discuss your idea/fix with the community before creating a pull request, and describe your changes before submitting a pull request. This is to ensure large feature PRs are discussed with the community first, before starting work on it. If the community does not want this feature or it is not relevant for Open WebUI as a project, it can be identified in the discussion before working on the feature and submitting the PR. **Before submitting, make sure you've checked the following:** - [x] **Target branch:** Verify that the pull request targets the `dev` branch. **PRs targeting `main` will be immediately closed.** - [x] **Description:** Provide a concise description of the changes made in this pull request down below. - [x] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description. - [x] **Documentation:** Add docs in [Open WebUI Docs Repository](https://github.com/open-webui/docs). Document user-facing behavior, environment variables, public APIs/interfaces, or deployment steps. - [x] **Dependencies:** Are there any new or upgraded dependencies? If so, explain why, update the changelog/docs, and include any compatibility notes. Actually run the code/function that uses updated library to ensure it doesn't crash. - [x] **Testing:** Perform manual tests to **verify the implemented fix/feature works as intended AND does not break any other functionality**. Include reproducible steps to demonstrate the issue before the fix. Test edge cases (URL encoding, HTML entities, types). Take this as an opportunity to **make screenshots of the feature/fix and include them in the PR description**. - [x] **Agentic AI Code:** Confirm this Pull Request is **not written by any AI Agent** or has at least **gone through additional human review AND manual testing**. If any AI Agent is the co-author of this PR, it may lead to immediate closure of the PR. - [x] **Code review:** Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards? - [x] **Design & Architecture:** Prefer smart defaults over adding new settings; use local state for ephemeral UI logic. Open a Discussion for major architectural or UX changes. - [x] **Git Hygiene:** Keep PRs atomic (one logical change). Clean up commits and rebase on `dev` to ensure no unrelated commits (e.g. from `main`) are included. Push updates to the existing PR branch instead of closing and reopening. - [x] **Title Prefix:** To clearly categorize this pull request, prefix the pull request title using one of the following: - **feat**: New feature # Changelog Entry ### Description - Upgraded the `Users` and `Evaluations` sidebar navigation components inside the Administration panel to inherently support native browser new-tab actions securely (such as middle-clicking to open in a background tab natively). ### Added - Inserted standard component `<a href...>` navigation mappings correctly tracking `evaluations` and `users` route tabs internally across both elements precisely targeting their respective endpoints. - Preserved drag safeguards seamlessly mapping `draggable="false"` accompanied by `class="... select-none"` identical to previous iteration templates across the rest of the Admin routes natively. ### Changed - Converted `<button>` components driving Single-Page-Application routing exclusively via `goto(route)` interactions into robust HTML5 native anchors identically structured identically parsing inside `src/lib/components/admin/Evaluations.svelte` and `src/lib/components/admin/Users.svelte`. ### Removed - Redundant pure UI `button` overrides previously suppressing local native HTML capabilities. --- ### Additional Information - **Context**: Just like the `admin/Settings.svelte` navigation pane addressed earlier, the sub-tabs governing the `Users` view (Overview vs Groups) and `Evaluations` views (Leaderboard vs Feedback) were rendering inside `on:click` bound `<button>` nodes blocking normal interaction commands via mouse. Adjusting them to natively route through `<a href...>` standard elements explicitly allows native mechanisms uninterrupted. - Related PR: https://github.com/open-webui/open-webui/pull/21721 ### Screenshots or Videos ### Before <img width="383" height="559" alt="image" src="https://github.com/user-attachments/assets/59a3e60e-bea8-4050-9e36-8ef6a28241ee" /> <img width="377" height="556" alt="image" src="https://github.com/user-attachments/assets/e016b3c2-27ec-4334-9784-a1dcf83d74b1" /> ### After <img width="383" height="559" alt="image" src="https://github.com/user-attachments/assets/b95c65bf-65d6-4079-933e-d303b691f90c" /> <img width="380" height="561" alt="image" src="https://github.com/user-attachments/assets/288875d5-2657-4ea8-b8cc-b9b576bd9cc2" /> ### Contributor License Agreement  By submitting this pull request, I confirm that I have read and fully agree to the [Contributor License Agreement (CLA)](https://github.com/open-webui/open-webui/blob/main/CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms. > [!NOTE] > Deleting the CLA section will lead to immediate closure of your PR and it will not be merged in. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-05-13 15:27:24 -05:00

GiteaMirror closed this issue

2026-05-13 15:27:26 -05:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#81114