Developer UI: pico tab links unreadable on darker background colors
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- node.js, typescript
- Domain
- accessibility, frontend
Research direction
Start by locating the developer UI's pico detail header and the existing logic that chooses the pico name text color from backgroundColor. Check how the About, Rulesets, Channels, Logging, Testing, and Relationships tab links are styled. Update the link color choice to keep the links readable on dark and light backgrounds, then verify the tabs against both the reported #4a6fa5 and a light color such as #f5bd45.
Written by the indexing model from the issue text.
Description
In the developer UI (pico-engine 1.9.5), a pico's detail header is
rendered in the pico's chosen backgroundColor, but the tab links
(About, Rulesets, Channels, Logging, Testing, Relationships) are
always the same blue.
On a mid-tone or dark background the links nearly disappear. Example:
a pico colored #4a6fa5 renders its name legibly (the name text already
adapts — white on dark, black on light) but the blue tab links on the
blue-gray background are very hard to read. Light backgrounds such as
amber (#f5bd45) read fine.
Suggestion: derive the tab link color from the background color's
luminance, the way the pico name's text color is already chosen —
e.g. use a light link color (or white) on dark backgrounds so the
contrast stays readable for any backgroundColor a user picks.
Workaround: choose only light background colors for picos.
- Dominant language
- TypeScript
- Stars
- 51
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No 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 Picolab/pico-engine
-
1 - Ready bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Picolab/pico-engine#496 ·
-
Difficulty 5/5 Over a week Newbie friendliness 42/100
Picolab/pico-engine#666 ·
-
documentation question
Difficulty 4/5 3-5 days Newbie friendliness 30/100
Picolab/pico-engine#662 ·
-
help wanted
Difficulty 4/5 3-5 days Newbie friendliness 30/100
Picolab/pico-engine#661 · 2 comments ·
-
Move to Peer DID v4Open
Difficulty 5/5 Over a week Newbie friendliness 20/100
Picolab/pico-engine#660 ·
All issues in Picolab/pico-engine
Similar issues
-
bot:ai-assisted component:platform-js status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
midnightntwrk/platform-js#69 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
ai-driven-qa bug claude Cosmetic
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
needs verification
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 13 days
-
Domain / chatbot New
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Inist-CNRS/lodex#3861 ·
Maintainers usually reply within 1 day