[PR #16166] [CLOSED] Custom theme changes #10847

New Issue

GiteaMirror · 2025-11-11T19:15:28-06:00

GiteaMirror commented

2025-11-11 19:15:28 -06:00

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/16166
Author: @jignasu-disney
Created: 7/31/2025
Status: ❌ Closed

Base: main ← Head: custom-theme

📝 Commits (1)

5ad850b Custom theme changes

📊 Changes

14 files changed (+119 additions, -112 deletions)

View changed files

📝 src/app.css (+1 -1)
📝 src/app.html (+4 -1)
📝 src/lib/components/channel/MessageInput.svelte (+2 -2)
📝 src/lib/components/channel/Navbar.svelte (+1 -1)
📝 src/lib/components/chat/Chat.svelte (+1 -1)
📝 src/lib/components/chat/MessageInput.svelte (+5 -5)
📝 src/lib/components/chat/Navbar.svelte (+1 -1)
📝 src/lib/components/chat/Placeholder.svelte (+4 -37)
📝 src/lib/components/chat/Settings/General.svelte (+1 -0)
📝 src/lib/components/chat/Suggestions.svelte (+7 -10)
📝 src/lib/components/common/Folder.svelte (+2 -2)
📝 src/lib/components/layout/Navbar.svelte (+1 -1)
📝 src/lib/components/layout/Sidebar.svelte (+30 -50)
📝 static/static/custom.css (+59 -0)

📄 Description

Pull Request Checklist

Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.

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

Target branch: Please verify that the pull request targets the dev branch.
Description: Provide a concise description of the changes made in this pull request.
Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
Testing: Have you written and run sufficient tests to validate the changes?
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?
Prefix: To clearly categorize this pull request, prefix the pull request title using one of the following:
- BREAKING CHANGE: Significant changes that may affect compatibility
- build: Changes that affect the build system or external dependencies
- ci: Changes to our continuous integration processes or workflows
- chore: Refactor, cleanup, or other non-functional code changes
- docs: Documentation update or addition
- feat: Introduces a new feature or enhancement to the codebase
- fix: Bug fix or error correction
- i18n: Internationalization or localization changes
- perf: Performance improvement
- refactor: Code restructuring for better maintainability, readability, or scalability
- style: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.)
- test: Adding missing tests or correcting existing tests
- WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry

Description

[Concisely describe the changes made in this pull request, including any relevant motivation and impact (e.g., fixing a bug, adding a feature, or improving performance)]

Added

[List any new features, functionalities, or additions]

Changed

[List any changes, updates, refactorings, or optimizations]

Deprecated

[List any deprecated functionality or features that have been removed]

Removed

[List any removed features, files, or functionalities]

Fixed

[List any fixes, corrections, or bug fixes]

Security

[List any new or updated security-related changes, including vulnerability fixes]

Breaking Changes

BREAKING CHANGE: [List any breaking changes affecting compatibility or functionality]

Additional Information

[Insert any additional context, notes, or explanations for the changes]
- [Reference any related issues, commits, or other relevant information]

Screenshots or Videos

[Attach any relevant screenshots or videos demonstrating the changes]

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.

_{🔄 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/16166 **Author:** [@jignasu-disney](https://github.com/jignasu-disney) **Created:** 7/31/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `custom-theme` --- ### 📝 Commits (1) - [`5ad850b`](https://github.com/open-webui/open-webui/commit/5ad850bac7fce936203620a92eb213676500abf8) Custom theme changes ### 📊 Changes **14 files changed** (+119 additions, -112 deletions) <details> <summary>View changed files</summary> 📝 `src/app.css` (+1 -1) 📝 `src/app.html` (+4 -1) 📝 `src/lib/components/channel/MessageInput.svelte` (+2 -2) 📝 `src/lib/components/channel/Navbar.svelte` (+1 -1) 📝 `src/lib/components/chat/Chat.svelte` (+1 -1) 📝 `src/lib/components/chat/MessageInput.svelte` (+5 -5) 📝 `src/lib/components/chat/Navbar.svelte` (+1 -1) 📝 `src/lib/components/chat/Placeholder.svelte` (+4 -37) 📝 `src/lib/components/chat/Settings/General.svelte` (+1 -0) 📝 `src/lib/components/chat/Suggestions.svelte` (+7 -10) 📝 `src/lib/components/common/Folder.svelte` (+2 -2) 📝 `src/lib/components/layout/Navbar.svelte` (+1 -1) 📝 `src/lib/components/layout/Sidebar.svelte` (+30 -50) 📝 `static/static/custom.css` (+59 -0) </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) and describe your changes before submitting a pull request. **Before submitting, make sure you've checked the following:** - [ ] **Target branch:** Please verify that the pull request targets the `dev` branch. - [ ] **Description:** Provide a concise description of the changes made in this pull request. - [ ] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description. - [ ] **Documentation:** Have you updated relevant documentation [Open WebUI Docs](https://github.com/open-webui/docs), or other documentation sources? - [ ] **Dependencies:** Are there any new dependencies? Have you updated the dependency versions in the documentation? - [ ] **Testing:** Have you written and run sufficient tests to validate the changes? - [ ] **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? - [ ] **Prefix:** To clearly categorize this pull request, prefix the pull request title using one of the following: - **BREAKING CHANGE**: Significant changes that may affect compatibility - **build**: Changes that affect the build system or external dependencies - **ci**: Changes to our continuous integration processes or workflows - **chore**: Refactor, cleanup, or other non-functional code changes - **docs**: Documentation update or addition - **feat**: Introduces a new feature or enhancement to the codebase - **fix**: Bug fix or error correction - **i18n**: Internationalization or localization changes - **perf**: Performance improvement - **refactor**: Code restructuring for better maintainability, readability, or scalability - **style**: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.) - **test**: Adding missing tests or correcting existing tests - **WIP**: Work in progress, a temporary label for incomplete or ongoing work # Changelog Entry ### Description - [Concisely describe the changes made in this pull request, including any relevant motivation and impact (e.g., fixing a bug, adding a feature, or improving performance)] ### Added - [List any new features, functionalities, or additions] ### Changed - [List any changes, updates, refactorings, or optimizations] ### Deprecated - [List any deprecated functionality or features that have been removed] ### Removed - [List any removed features, files, or functionalities] ### Fixed - [List any fixes, corrections, or bug fixes] ### Security - [List any new or updated security-related changes, including vulnerability fixes] ### Breaking Changes - **BREAKING CHANGE**: [List any breaking changes affecting compatibility or functionality] --- ### Additional Information - [Insert any additional context, notes, or explanations for the changes] - [Reference any related issues, commits, or other relevant information] ### Screenshots or Videos - [Attach any relevant screenshots or videos demonstrating the changes] ### Contributor License Agreement By submitting this pull request, I confirm that I have read and fully agree to the [Contributor License Agreement (CLA)](/CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms. --- <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 2025-11-11 19:15:28 -06:00

GiteaMirror closed this issue

2025-11-11 19:15:28 -06:00

GiteaMirror referenced this issue

2026-05-06 00:22:41 -05:00

[GH-ISSUE #24207] issue: Safari cannot establish WebSocket on 0.9.2 (direct port, no reverse proxy) #58896

Sign in to join this conversation.