Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RangeInput not respecting background color opacity #6739

Open
taysea opened this issue Apr 6, 2023 · 0 comments · May be fixed by #7052
Open

RangeInput not respecting background color opacity #6739

taysea opened this issue Apr 6, 2023 · 0 comments · May be fixed by #7052
Assignees
Labels
bug issue that does not match design or documentation and requires code changes to address

Comments

@taysea
Copy link
Collaborator

taysea commented Apr 6, 2023

Expected Behavior

RangeInput should accurately render track colors, and include any opacity information (such as a HEX string that includes opacity)

Actual Behavior

The opacity is not being applied. For example, if a theme specifies #0000005C, the 5C opacity of 36% isn't being honored.

URL, screen shot, or Codepen exhibiting the issue

The HPE theme defines the track as "border" (#0000005C), but it's being rendered as #000000.

https://design-system.hpe.design/components/rangeinput?q=rangein

Steps to Reproduce

Your Environment

  • Grommet version:
  • Browser Name and version:
  • Operating System and version (desktop or mobile):
@taysea taysea added the bug issue that does not match design or documentation and requires code changes to address label Apr 6, 2023
@taysea taysea added this to Triage in Grommet/Design System Backlog via automation Apr 6, 2023
@taysea taysea moved this from Triage to Next Active in Grommet/Design System Backlog Apr 6, 2023
@Sulaymon333 Sulaymon333 linked a pull request Dec 8, 2023 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug issue that does not match design or documentation and requires code changes to address
Projects
Development

Successfully merging a pull request may close this issue.

2 participants