Status colors need updating
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
Research direction
Start by locating the Android status color definitions and compare the danger and warning values with the attached Fluent 2 Figma color comparison. Done means the code uses the current Fluent 2 colors for both statuses and the relevant tests or visual checks pass.
Written by the indexing model from the issue text.
Description
All environments
Please provide a reproduction of the bug:
Fluent 2 mobile status colors were updated a few years ago, but the updates were not made in code.
Actual behavior:
Danger and warning colors do not reflect most recent Fluent 2 Android Figma colors
Expected behavior:
Danger and warning colors are expected to match the Figma Fluent 2 colors
Priorities and help requested:
Are you willing to submit a PR to fix? (No)
Requested priority: (High)
Products/applications affected:
Color comparison
- Dominant language
- Kotlin
- Stars
- 677
- Forks
- 127
- PR merge metrics
- No merged PRs in 30d
Getting set up
- 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 microsoft/fluentui-android
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
microsoft/fluentui-android#836 ·
-
Ui/animation bugOpen
Difficulty 3/5 1-2 days Newbie friendliness 55/100
microsoft/fluentui-android#835 ·
All issues in microsoft/fluentui-android
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
trakt/trakt-android#425 ·
Maintainers usually reply within 1 day
-
Raijin Scans (FR)OpenBug Domain changed
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
keiyoushi/extensions-source#19644 · 1 reaction ·
Maintainers usually reply within 1 day
-
node: disconnection push notification is logged as "Unknown notification" instead of the disconnect warningPossibly taken @datatrigger claimed this 1 day ago. Openbug 🐞 Untriaged user issue
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
valkey-io/valkey-glide#7278 ·
Maintainers usually reply within 2 days
-
enhancement triaged
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 3 days
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
mobile-dev-inc/Maestro#3659 · 1 comment ·
Maintainers usually reply within 1 day