[PR #24392] fix: improve banner layout on mobile devices #66495

New Issue

GiteaMirror · 2026-05-06T12:53:36-05:00

GiteaMirror commented

2026-05-06 12:53:36 -05:00

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/24392
Author: @jqqin
Created: 5/5/2026
Status: 🔄 Open

Base: dev ← Head: fix/banner-mobile-layout

📝 Commits (1)

7002815 fix: improve banner layout on mobile devices

📊 Changes

2 files changed (+32 additions, -3 deletions)

View changed files

📝 src/lib/components/chat/Navbar.svelte (+31 -2)
📝 src/lib/components/common/Banner.svelte (+1 -1)

📄 Description

Banners previously stacked badge and text vertically on mobile due to flex-col, and too many banners/ long banners could block page content. This fixes both issues by using inline flex-row layout on all screen sizes and adding a collapsible container with a "Show more" toggle on mobile, desktop behavior is unchanged.

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:
- 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

Fixed banner component layout on mobile devices where badge (INFO/WARNING/etc.) and content text were stacking vertically instead of displaying inline, and added a collapsible container to prevent excessive banners from blocking page content

Added

"Show more" / "Show less" toggle button on mobile when banners overflow the visible area
Overflow detection using afterUpdate to determine when banners are clipped

Changed

Banner component inner layout from flex-col md:flex-row to flex-row for consistent inline display across all screen sizes
Banner container in Navbar to use max-h-28 overflow-hidden on mobile with md:max-h-none on desktop

Deprecated

N/A

Removed

N/A

Fixed

Banner badge and text stacking vertically on mobile instead of displaying inline
Multiple banners or long banner content blocking the main chat interface on mobile devices

Security

N/A

Breaking Changes

N/A

Additional Information

Changes are limited to two files: Banner.svelte (1 line CSS fix) and Navbar.svelte (collapsible container logic)
The collapsible toggle is mobile-only (md:hidden), desktop behavior is unchanged
Uses overflow-hidden instead of overflow-y-auto on mobile to avoid iOS Safari pull-to-refresh issues with overscroll-behavior: contain not being fully supported
Tested on iOS Safari and desktop Chrome

Screenshots or Videos

Before — stacked layout:

Mobile: banner badge and text stack vertically, multiple banners block the page content

After — inline layout with collapsible container:

Mobile: badge and text display inline, excess banners are collapsed behind a "Show more" toggle

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/24392 **Author:** [@jqqin](https://github.com/jqqin) **Created:** 5/5/2026 **Status:** 🔄 Open **Base:** `dev` ← **Head:** `fix/banner-mobile-layout` --- ### 📝 Commits (1) - [`7002815`](https://github.com/open-webui/open-webui/commit/7002815fc278c32f9a37ed12f01c8f693a4ede4f) fix: improve banner layout on mobile devices ### 📊 Changes **2 files changed** (+32 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `src/lib/components/chat/Navbar.svelte` (+31 -2) 📝 `src/lib/components/common/Banner.svelte` (+1 -1) </details> ### 📄 Description Banners previously stacked badge and text vertically on mobile due to `flex-col`, and too many banners/ long banners could block page content. This fixes both issues by using inline `flex-row` layout on all screen sizes and adding a collapsible container with a "Show more" toggle on mobile, desktop behavior is unchanged.  # 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: - **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 - Fixed banner component layout on mobile devices where badge (INFO/WARNING/etc.) and content text were stacking vertically instead of displaying inline, and added a collapsible container to prevent excessive banners from blocking page content ### Added - "Show more" / "Show less" toggle button on mobile when banners overflow the visible area - Overflow detection using `afterUpdate` to determine when banners are clipped ### Changed - Banner component inner layout from `flex-col md:flex-row` to `flex-row` for consistent inline display across all screen sizes - Banner container in Navbar to use `max-h-28 overflow-hidden` on mobile with `md:max-h-none` on desktop ### Deprecated - N/A ### Removed - N/A ### Fixed - Banner badge and text stacking vertically on mobile instead of displaying inline - Multiple banners or long banner content blocking the main chat interface on mobile devices ### Security - N/A ### Breaking Changes - N/A --- ### Additional Information - Changes are limited to two files: `Banner.svelte` (1 line CSS fix) and `Navbar.svelte` (collapsible container logic) - The collapsible toggle is mobile-only (`md:hidden`), desktop behavior is unchanged - Uses `overflow-hidden` instead of `overflow-y-auto` on mobile to avoid iOS Safari pull-to-refresh issues with `overscroll-behavior: contain` not being fully supported - Tested on iOS Safari and desktop Chrome ### Screenshots or Videos Before — stacked layout: Mobile: banner badge and text stack vertically, multiple banners block the page content <img width="591" height="850" alt="image" src="https://github.com/user-attachments/assets/6080acd4-3aeb-4818-9750-f5dcf9cc1ca6" /> After — inline layout with collapsible container: Mobile: badge and text display inline, excess banners are collapsed behind a "Show more" toggle <img width="632" height="504" alt="image" src="https://github.com/user-attachments/assets/cc063708-a71a-4afa-ba6a-135c418cdb6e" /> <img width="656" height="517" alt="image" src="https://github.com/user-attachments/assets/d4d9c422-f45b-413b-9384-8862a651baf1" /> ### Contributor License Agreement  - [x] 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 12:53:36 -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#66495