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

Make disabled state of Range input more obvious #5417

Open
Dinika opened this issue Nov 29, 2024 · 3 comments
Open

Make disabled state of Range input more obvious #5417

Dinika opened this issue Nov 29, 2024 · 3 comments
Labels
Triaged: v4 Triaged, to be implemented as part of Vanilla v4 Vanilla WG Task owned by Vanilla Working Group WG: Validated Validate working group proposals

Comments

@Dinika
Copy link
Contributor

Dinika commented Nov 29, 2024

Component/pattern to amend

Range Input

Visual

MissingLabelsForInput

Context

I found the disabled Range input to be visually very similar to the non-disabled version because of the following reasons:

  • The color for the disabled range input looks very similar to the non-disabled version.
  • The pointer also does not change to the "not-allowed" or "default" state. It keeps being a "cursor" type.

In comparison other form inputs (like the Checkbox) change the color to gray and the cursor to "not-allowed" when the input is disabled.

@Dinika Dinika added the WG: Proposal Working group proposals label Nov 29, 2024
Copy link

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/WD-17364.

This message was autogenerated

@bartaz bartaz added the Vanilla WG Task owned by Vanilla Working Group label Nov 29, 2024
@bartaz
Copy link
Member

bartaz commented Nov 29, 2024

Thanks for your report. Indeed, currently we only use opacity 0.5 to mark range input as disabled.
We will discuss how to improve it.

@bartaz
Copy link
Member

bartaz commented Dec 11, 2024

Lyubo: we should make the blue track gray.

Validated, ready for implementation.

@bartaz bartaz added WG: Validated Validate working group proposals Triaged: v4 Triaged, to be implemented as part of Vanilla v4 and removed WG: Proposal Working group proposals labels Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Triaged: v4 Triaged, to be implemented as part of Vanilla v4 Vanilla WG Task owned by Vanilla Working Group WG: Validated Validate working group proposals
Projects
None yet
Development

No branches or pull requests

2 participants