github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 10:58:17 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #22733] issue: Full Page Reload on User Menu Playground and Admin Panel Navigation #19800

New Issue
Closed
opened 2026-04-20 02:17:59 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-20 02:17:59 -05:00
Owner
Copy Link

Originally created by @silentoplayz on GitHub (Mar 16, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22733

Check Existing Issues

  • I have searched for any existing and/or related issues.
  • I have searched for any existing and/or related discussions.
  • I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.8.10

Ollama Version (if applicable)

v0.18.0

Operating System

Ubuntu 24.04.4 LTS

Browser (if applicable)

Mozilla Firefox Snap for Ubuntu v148.0.2 (64-bit) / Google Chrome v146.0.7680.80 (Official Build) (64-bit)

Confirmation

  • I have read and followed all instructions in README.md.
  • I am using the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.
  • I have provided every relevant configuration, setting, and environment variable used in my setup.
  • I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
  • I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
  • Start with the initial platform/version/OS and dependencies used,
  • Specify exact install/launch/configure commands,
  • List URLs visited, user input (incl. example values/emails/passwords if needed),
  • Describe all options and toggles enabled or changed,
  • Include any files or environmental changes,
  • Identify the expected and actual result at each stage,
  • Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

Clicking on the Playground and Admin Panel buttons in the user menu should route instantly to the respective pages as part of the Single Page Application (SPA) navigation without triggering a full page reload (no splash screen), which is consistent with the previous behavior.

Actual Behavior

Clicking on the Playground or Admin Panel links in the user menu triggers a full page reload in the browser. The Open WebUI splash screen flashes before the requested page finishes loading.

Steps to Reproduce

  1. Start an Open WebUI instance (v0.8.10) using Docker Desktop on Ubuntu 24.04.4 LTS.
  2. Open Mozilla Firefox v148.0.2 and log in to the interface.
  3. Open the user menu modal by clicking the user profile icon at the bottom-left of the sidebar.
  4. Click on Playground.
  5. Observe that the browser performs a full page reload (the splash screen is briefly visible) instead of using client-side routing.
  6. Return to the chat view or stay on the Playground, and open the user menu modal again.
  7. Click on Admin Panel.
  8. Observe that the system again performs a full page reload.

Logs & Screenshots

Not applicable (this is an unexpected regular HTTP document navigation rather than an application-crashing bug, so there are no relevant errors in the console or Docker logs).

Additional Information

The issue stems from the source code in src/lib/components/layout/Sidebar/UserMenu.svelte. The Playground and Admin Panel items are implemented using <DropdownMenu.Item as="a" href="...">.

In Bits-UI, using as="a" with an href bypasses SvelteKit's client-side router and tells the browser to perform a native top-level navigation, which triggers the full page reload instead of instantly resolving the component. Using SvelteKit's goto() programmatically in the on:click block or verifying SvelteKit's data-sveltekit-preload-data tags would resolve this.

Originally created by @silentoplayz on GitHub (Mar 16, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/22733 ### Check Existing Issues - [x] I have searched for any existing and/or related issues. - [x] I have searched for any existing and/or related discussions. - [x] I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!). - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.8.10 ### Ollama Version (if applicable) v0.18.0 ### Operating System Ubuntu 24.04.4 LTS ### Browser (if applicable) Mozilla Firefox Snap for Ubuntu v148.0.2 (64-bit) / Google Chrome v146.0.7680.80 (Official Build) (64-bit) ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior Clicking on the `Playground` and `Admin Panel` buttons in the user menu should route instantly to the respective pages as part of the Single Page Application (SPA) navigation without triggering a full page reload (no splash screen), which is consistent with the previous behavior. ### Actual Behavior Clicking on the `Playground` or `Admin Panel` links in the user menu triggers a full page reload in the browser. The Open WebUI splash screen flashes before the requested page finishes loading. ### Steps to Reproduce 1. Start an Open WebUI instance (v0.8.10) using Docker Desktop on Ubuntu 24.04.4 LTS. 2. Open Mozilla Firefox v148.0.2 and log in to the interface. 3. Open the user menu modal by clicking the user profile icon at the bottom-left of the sidebar. 4. Click on `Playground`. 5. Observe that the browser performs a full page reload (the splash screen is briefly visible) instead of using client-side routing. 6. Return to the chat view or stay on the Playground, and open the user menu modal again. 7. Click on `Admin Panel`. 8. Observe that the system again performs a full page reload. ### Logs & Screenshots Not applicable (this is an unexpected regular HTTP document navigation rather than an application-crashing bug, so there are no relevant errors in the console or Docker logs). ### Additional Information The issue stems from the source code in `src/lib/components/layout/Sidebar/UserMenu.svelte`. The `Playground` and `Admin Panel` items are implemented using `<DropdownMenu.Item as="a" href="...">`. In Bits-UI, using `as="a"` with an `href` bypasses SvelteKit's client-side router and tells the browser to perform a native top-level navigation, which triggers the full page reload instead of instantly resolving the component. Using SvelteKit's `goto()` programmatically in the `on:click` block or verifying SvelteKit's `data-sveltekit-preload-data` tags would resolve this.
GiteaMirror added the confirmed issuebug labels 2026-04-20 02:18:00 -05:00
GiteaMirror commented 2026-04-20 02:18:02 -05:00
Author
Owner
Copy Link

@silentoplayz commented on GitHub (Mar 22, 2026):

This issue has been resolved on the dev branch with 7ffcd3908e.

<!-- gh-comment-id:4106009786 --> @silentoplayz commented on GitHub (Mar 22, 2026): This issue has been resolved on the `dev` branch with https://github.com/open-webui/open-webui/commit/7ffcd3908ee90f88a4c4684d6cd6e75efd117461.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug confirmed issue
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#19800
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?