[PR #21722] [CLOSED] fix: conditionally hide user status emojis based on global enable_user_status feature flag config #65096

Closed
opened 2026-05-06 10:52:19 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/21722
Author: @silentoplayz
Created: 2/22/2026
Status: Closed

Base: devHead: fix/user-modal-status-emoji


📝 Commits (2)

  • 5229d77 fix(ui): conditionally hide user status emojis in modal based on global enable_user_status feature flag config
  • 5922587 fix(ui): selectively hide user status emojis in sidebar dm channels based on global enable_user_status flag

📊 Changes

2 files changed (+4 additions, -4 deletions)

View changed files

📝 src/lib/components/channel/Messages/Message/UserStatus.svelte (+2 -2)
📝 src/lib/components/layout/Sidebar/ChannelItem.svelte (+2 -2)

📄 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 visual persistence bug where user status emojis would incorrectly remain rendered inside the profile modal hover preview component (UserStatus.svelte) even when user statuses were globally disabled via settings or environment variables (ENABLE_USER_STATUS=false).

Added

  • Appended $config?.features?.enable_user_status conditional wrapping correctly encapsulating the entire emoji container layout explicitly.
  • Imported the global config user preferences layout store precisely inside src/lib/components/channel/Messages/Message/UserStatus.svelte correctly enabling environment variable validation parsing safely.

Fixed

  • Solved the emoji isolation bypass bug internally exposing user status widgets regardless of configuration parameters natively on UserList.svelte hover profiles gracefully.

Additional Information

  • Context: The UserStatus.svelte module previously only evaluated the presence of user?.status_emoji or user?.status_message inside its internal HTML markup conditional branches without cross-referencing $config?.features?.enable_user_status explicitly. This resulted in the status payload conditionally hiding text if stripped serverside natively by configurations overriding it internally, yet continuing to generate empty ghost emoji blocks due to the payload conditionally clearing improperly locally when text drops natively. Adding the explicit condition ensures synchronicity indefinitely.

Screenshots or Videos

Before

image image image

After

image image image

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/21722 **Author:** [@silentoplayz](https://github.com/silentoplayz) **Created:** 2/22/2026 **Status:** ❌ Closed **Base:** `dev` ← **Head:** `fix/user-modal-status-emoji` --- ### 📝 Commits (2) - [`5229d77`](https://github.com/open-webui/open-webui/commit/5229d77ea7d41d8a4ed333b903d6fe8f4c862f0c) fix(ui): conditionally hide user status emojis in modal based on global enable_user_status feature flag config - [`5922587`](https://github.com/open-webui/open-webui/commit/5922587f986dd3b3905b4ef5f842eb5e07e1ada3) fix(ui): selectively hide user status emojis in sidebar dm channels based on global enable_user_status flag ### 📊 Changes **2 files changed** (+4 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `src/lib/components/channel/Messages/Message/UserStatus.svelte` (+2 -2) 📝 `src/lib/components/layout/Sidebar/ChannelItem.svelte` (+2 -2) </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 visual persistence bug where user status emojis would incorrectly remain rendered inside the profile modal hover preview component (`UserStatus.svelte`) even when user statuses were globally disabled via settings or environment variables (`ENABLE_USER_STATUS=false`). ### Added - Appended `$config?.features?.enable_user_status` conditional wrapping correctly encapsulating the entire emoji container layout explicitly. - Imported the global `config` user preferences layout store precisely inside `src/lib/components/channel/Messages/Message/UserStatus.svelte` correctly enabling environment variable validation parsing safely. ### Fixed - Solved the emoji isolation bypass bug internally exposing user status widgets regardless of configuration parameters natively on `UserList.svelte` hover profiles gracefully. --- ### Additional Information - **Context**: The `UserStatus.svelte` module previously only evaluated the presence of `user?.status_emoji` or `user?.status_message` inside its internal HTML markup conditional branches without cross-referencing `$config?.features?.enable_user_status` explicitly. This resulted in the status payload conditionally hiding text if stripped serverside natively by configurations overriding it internally, yet continuing to generate empty ghost emoji blocks due to the payload conditionally clearing improperly locally when text drops natively. Adding the explicit condition ensures synchronicity indefinitely. ### Screenshots or Videos ### Before <img width="446" height="278" alt="image" src="https://github.com/user-attachments/assets/b9589a37-d65c-47c4-8235-8ffd5658ccf5" /> <img width="221" height="189" alt="image" src="https://github.com/user-attachments/assets/5dcc53e2-ef0d-47bd-9a44-8592bb7ce41f" /> <img width="1739" height="96" alt="image" src="https://github.com/user-attachments/assets/0ad5f04d-055c-4565-9371-acd6063da5fc" /> ### After <img width="446" height="278" alt="image" src="https://github.com/user-attachments/assets/b3ead4fa-e630-41a3-b87b-a2d0bb649bf6" /> <img width="221" height="189" alt="image" src="https://github.com/user-attachments/assets/f269c29c-6142-4e2c-a393-710ed24e9424" /> <img width="1739" height="96" alt="image" src="https://github.com/user-attachments/assets/f5b5e2c4-f78c-463a-b49d-7b2c951e87e4" /> ### 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-06 10:52:19 -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#65096