Notifications panel is see-through in dark theme: the side panel's text shows through it
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 76/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- css
- Domain
- frontend
Research direction
The bug is in the background of the .notification-center selector, which the report says uses an rgba color with alpha 0.92 and no backdrop blur. Find the stylesheet that defines that selector and check the dark-theme rule for it. To verify, open a chat with the right-hand panel in dark theme, click the bell with a notification present, and confirm the panel text no longer shows through. Done when the panel is opaque in dark theme and the notification list looks right in light theme too.
Written by the indexing model from the issue text.
Description
Notifications panel is see-through in dark theme: the side panel's text shows through it.
Steps
- Dark theme, a chat open with the right 'This chat' panel.
- Click the bell (Notifications) with at least one notification.
Expected: An opaque panel.
Actual: Text of the panel underneath ('This chat', 'Websites None from GAIA's web tools', 'Cost About $0.0011') is visible inside the notification list; .notification-center background is rgba with alpha 0.92 and no backdrop blur.
Build: v0.26.0-rc24 packaged Windows app (isolated profile, chat on a cloud model)
Found by: the v0.26.0-rc24 final release test, finding F27
🔍 Technical details
- Suspected area: NotificationCenter css .notification-center background
- Dominant language
- Python
- Stars
- 1.6k
- Forks
- 169
- Avg merge
- 12h 19m
- Merged PRs (30d)
- 777
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from amd/gaia
-
agent-ui bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug needs-human p2
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
bug cli p2
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
bug cli needs-human p3
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
agent-ui bug p3
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
Similar issues
-
area:core-platform effort:S priority:P3 risk:night-safe status:ready type:test
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
randomparity/kdive#3620 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
FinanceFlash/unvibecode#760 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
google-research/google-research#3470 ·
Maintainers usually reply within 21 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
mrvautin/ha-workouts#11 ·