[ui5-step-input]: wrong opacity on disabled state

Open Beginner friendly
#14,061 1 comment 0 reactions 0 assignees View on GitHub

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
typescript
Domain
design, frontend

Research direction

Start with the ui5-step-input component and compare its disabled appearance with the normal input using the linked isolated playground example. Trace the disabled-state styling and verify in Chrome that the step input opacity matches the normal input; done means the two disabled states have the same opacity.

Written by the indexing model from the issue text.

Description

bug Low Prio TOPIC B
Bug Description

Compare the normal input and step input disabled opacity.

Affected Component

ui5-step-input

Expected Behaviour

No response

Isolated Example

https://ui5.github.io/webcomponents/nightly/play/#eNp9UsFqGzEQ_RVFp8RYVnMIlM3ahKYt9NIWmhwKe5GlcaxUO1okrV1j_O8dyWuzadOAYT1vZp7evJk9t2jg92ydWserPUfVAq_G4JRrjwkwEVxfCME6p3ZPwfdoxMo7w4RYNFhffPx2__Dz-yeWmzKQv8wpfJo3HLDhhGUUlKF_jH51TDsHOZhU6NNlZWBlEcwV2xNmbMwPVQw9wi0Bh9xf2Et-5YMGI7R3PghlnvuYXtSyWp74c9BCUkyvVYiQSNDjw2fxvmgaUnluwjcWtp0PqeFsmJrArTVpPTewsRpECabMok1WORG1cjC_nr0byJJN9OYP1XYOanmMaGw5zF0vvdmxIoyIl0r_Gpwsc1Rso8KlEFF1H86p-5y5ui38tbGbc3dRUrHrmwDtMfvKdgTgsCHK9_ZGYN8uIQiLXZ-yyWrpwCxq-XduMdS_Wniu-P89SJJaHIk62C6xtOuy6Nab3gHZG4POobI4e44kn9ZVCktvdulo23BMb07GD9MT0eiET8j4fuVkzLK2BthENmjbvHPW8JkcpWPfZbjIo6P6t7coeNF_R-bILSy1JwTpzUg2xCS_FmO_ZNdOdPxw-ANY1TWh

Steps to Reproduce

...

Log Output, Stack Trace or Screenshots

No response

Priority

None

UI5 Web Components Version

nightly

Browser

Chrome

Operating System

No response

Additional Context

No response

Organization

No response

Declaration
  • I’m not disclosing any internal or sensitive information.
Dominant language
TypeScript
Stars
1.8k
Forks
285
Avg merge
3d 2h
Merged PRs (30d)
59

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from UI5/webcomponents

All issues in UI5/webcomponents

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.