mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-07 03:18:23 -05:00
[GH-ISSUE #22538] issue: can't read the page because linear gradient makes text too dim #58405
Reference in New Issue
Block a user
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?
Originally created by @6000years on GitHub (Mar 10, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22538
Check Existing Issues
Installation Method
Docker
Open WebUI Version
0.8.10
Ollama Version (if applicable)
No response
Operating System
fedora 43
Browser (if applicable)
firefox
Confirmation
README.md.Expected Behavior
I should be able to read the conversation with the llm.
Actual Behavior
Too difficult to read (text too dim).
Steps to Reproduce
Click 'New Conversation'. Prompt the llm.
Logs & Screenshots
Additional Information
just a guess, but maybe the intention was to apply the gradient just to the top navbar header. in fact the gradient is spilling over to the whole height of the page, and I can't read it.
However if I duplicate the tab, or click on the conversation title in the left sidebar, then the gradient goes away.
@ShirasawaSama commented on GitHub (Mar 11, 2026):
What is the version of your browser's kernel?
@6000years commented on GitHub (Mar 11, 2026):
It's firefox developer edition 149.0 beta5.
After looking at this a bit more, I've noticed that the problem is a bit worse than I originally noted because the fixes (F5, duplicate tab, click on conversation in sidebar) only last a few seconds.
I see that the offending element «div id="navbar-bg-gradient-to-b"» has a computed value for bottom of -40px which comes from both
.-bottom-10: calc(var(--spacing)*-10)
and
.inset-0: calc(var(--spacing)*0)
with --spacing set at .25rem
If I untick/deactivate those 2 css props then the computed value of bottom is removed (goes to browser default) and the issue goes away.
@tjbck commented on GitHub (Mar 15, 2026):
Unable to reproduce, likely a browser bug/error. Keep us posted.