[PR #21704] [MERGED] fix: prevent text-selection ghost dragging on playground navigation tabs #113533

Closed
opened 2026-05-18 13:56:53 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/21704
Author: @silentoplayz
Created: 2/21/2026
Status: Merged
Merged: 2/21/2026
Merged by: @tjbck

Base: devHead: fix/playground-nav-drag-glitch


📝 Commits (1)

  • 2bde923 fix(ui): prevent text-selection ghost dragging on playground navigation tabs

📊 Changes

1 file changed (+7 additions, -4 deletions)

View changed files

📝 src/routes/(app)/playground/+layout.svelte (+7 -4)

📄 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:
    • fix: Bug fix or error correction

Changelog Entry

Description

  • Fixed a bug where the top navigation tabs in the Playground could be dragged natively as ghost images via standard HTML5 pointer dragging and bounding-box text-selections.

Added

  • Appended draggable="false" to the individual Chat, Completions, and Images navigation anchor tabs natively in src/routes/(app)/playground/+layout.svelte to prevent standard element tearing during pointer drags.
  • Applied the select-none Tailwind utility class directly to the parent <nav> container header to prevent users from accidentally highlighting the UI wrapper padding and dragging the entire container as one massive ghost block.

Fixed

  • Eliminated native HTML5 ghost dragging anomalies on the top Playground navigation bar tabs perfectly.

Additional Information

  • Context: The <a> tags naturally used for top-level navigation inside the playground routes previously lacked native drag constraints, carelessly allowing them to be picked up and dragged which created visual glitch cursors natively in HTML5. While appending draggable="false" gracefully prevented tearing each individual element itself, highlighting empty space via mouse-driven text-selection blindly bypassed the first fix—causing the entire parent flex container block to natively drag identically as one giant ghost chunk. By securely elevating select-none precisely to the outermost <nav> header boundary itself and concurrently preserving draggable="false" on the internal link children natively, the entire routing header is now strictly immune natively to phantom dragging sweeps across the entire screen unconditionally.

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/21704 **Author:** [@silentoplayz](https://github.com/silentoplayz) **Created:** 2/21/2026 **Status:** ✅ Merged **Merged:** 2/21/2026 **Merged by:** [@tjbck](https://github.com/tjbck) **Base:** `dev` ← **Head:** `fix/playground-nav-drag-glitch` --- ### 📝 Commits (1) - [`2bde923`](https://github.com/open-webui/open-webui/commit/2bde92358fe360049ba81262c89ffbcfe7737f24) fix(ui): prevent text-selection ghost dragging on playground navigation tabs ### 📊 Changes **1 file changed** (+7 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `src/routes/(app)/playground/+layout.svelte` (+7 -4) </details> ### 📄 Description <!-- ⚠️ CRITICAL CHECKS FOR CONTRIBUTORS (READ, DON'T DELETE) ⚠️ 1. Target the `dev` branch. PRs targeting `main` will be automatically closed. 2. Do NOT delete the CLA section at the bottom. It is required for the bot to accept your PR. --> # 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: - **fix**: Bug fix or error correction # Changelog Entry ### Description - Fixed a bug where the top navigation tabs in the Playground could be dragged natively as ghost images via standard HTML5 pointer dragging and bounding-box text-selections. ### Added - Appended `draggable="false"` to the individual `Chat`, `Completions`, and `Images` navigation anchor tabs natively in `src/routes/(app)/playground/+layout.svelte` to prevent standard element tearing during pointer drags. - Applied the `select-none` Tailwind utility class directly to the parent `<nav>` container header to prevent users from accidentally highlighting the UI wrapper padding and dragging the entire container as one massive ghost block. ### Fixed - Eliminated native HTML5 ghost dragging anomalies on the top Playground navigation bar tabs perfectly. --- ### Additional Information - **Context**: The `<a>` tags naturally used for top-level navigation inside the `playground` routes previously lacked native drag constraints, carelessly allowing them to be picked up and dragged which created visual glitch cursors natively in HTML5. While appending `draggable="false"` gracefully prevented tearing each individual element itself, highlighting empty space via mouse-driven text-selection blindly bypassed the first fix—causing the entire parent flex container block to natively drag identically as one giant ghost chunk. By securely elevating `select-none` precisely to the outermost `<nav>` header boundary itself and concurrently preserving `draggable="false"` on the internal link children natively, the entire routing header is now strictly immune natively to phantom dragging sweeps across the entire screen unconditionally. ### Contributor License Agreement <!-- 🚨 DO NOT DELETE THE TEXT BELOW 🚨 Keep the "Contributor License Agreement" confirmation text intact. Deleting it will trigger the CLA-Bot to INVALIDATE your PR. --> 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-18 13:56:53 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#113533