Color Picker Popup Is Obscured On "Guides -> Theming -> Creating Dynamic Theme Colors" Documentation On Both v5 and v6
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
- react-native, typescript
- Domain
- documentation, frontend
Research direction
Start at the React Native Paper documentation page for Guides → Theming → Creating Dynamic Theme Colors and inspect the custom theme builder, especially the element using the color-picker-popup class. Reproduce the issue in Firefox with each color picker, then verify that the popup and manual color input are fully visible without breaking the surrounding layout.
Written by the indexing model from the issue text.
Description
Current behaviour
Color picker popup is not fully shown. I can't fill the color manually because the input is obscured. This happens for primary, secondary, and tertiary color pickers. I don't know if this happens on another platform, but I'm currently using Firefox 155.0 at the time of writing.
Expected behaviour
The color picker should be fully shown.
How to reproduce?
- Go to React Native Paper documentation site (v5 or v6).
- Navigate to Guides -> Theming -> Creating Dynamic Theme Colors.
- Scroll down to the custom theme builder / color picker section and click any color input.
Preview
Primary Color Picker
Secondary Color Picker
Tertiary Color Picker
What have you tried so far?
I was able to show the whole thing by changing the "div" element with "color-picker-popup" class, "position" style to "relative" instead of "absolute". But it also grows the parent "tr" element.
Modified Element
Your Environment
| software | version |
|---|---|
| ios | N/A |
| android | N/A |
| react-native | N/A |
| react-native-paper | v5 / v6 (docs site) |
| node | N/A |
| npm or yarn | N/A |
| expo sdk | N/A |
| Firefox | 155.0 |
- Dominant language
- TypeScript
- Stars
- 14.5k
- Forks
- 2.2k
- Avg merge
- 5d 23h
- Merged PRs (30d)
- 11
Contributor 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 callstack/react-native-paper
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
callstack/react-native-paper#5096 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
callstack/react-native-paper#5003 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
callstack/react-native-paper#4951 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
callstack/react-native-paper#4881 ·
-
feature request
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
callstack/react-native-paper#4863 · 1 comment ·
All issues in callstack/react-native-paper
Similar issues
-
S: triage
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
fix(errors): EHOSTUNREACH from a happy-eyeballs connect is reported as a resolver error (STAMP-80) Open
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
snapshot-labs/stamp#666 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
GauravKarakoti/SecureFlow#1070 · 1 comment ·
-
feature:Languages/Translations good first issue ready Web
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
digitalfabrik/integreat-app#4394 ·