Make "read-only" input more obvious
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 56/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- accessibility, design, frontend
Research direction
Start with the i15-1 puck-selection component and review Atlas Issue #146 plus the linked PR discussion for the existing read-only behavior. Make read-only components visually distinctive without treating them as disabled, then verify that the value remains focusable, announced, and in the tab order.
Written by the indexing model from the issue text.
Description
Atlas Issue #146: For the i15-1 puck selection a component was made read-only (see discussion) but it's not obvious to a user that this is read-only at a glance. We should make read only components more visually distinctive
What is the difference between Disabled and Read-only?
In a nut shell:
• Disabled: field doesn’t apply right now (irrelevant). It is removed from tab order (skipped by assistive technologies), not submitted as data. Example: when a field is inactive, because you need to select something else before this one is relevant, or, when items are being loaded into a list (disabled until active).
• Read-only: value still matters, just locked. Stays focusable, announced, and in tab order. The user needs to read it, not just see it greyed out. With a normal text field,read-only means you can select it or copy text from it (with Select I'm not so sure). Example: the current state of an item is locked, but current selection is viable information, or, see the status assigned by another user, but you cannot change it yourself.
- Dominant language
- TypeScript
- Stars
- 8
- Forks
- 3
- Avg merge
- 2d 6h
- 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 DiamondLightSource/sci-react-ui
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
needs-triage
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
accepted
Difficulty 4/5 3-5 days Newbie friendliness 68/100
-
needs-triage
Difficulty 5/5 Over a week Newbie friendliness 45/100
-
needs-triage
Difficulty 5/5 Over a week Newbie friendliness 35/100
DiamondLightSource/sci-react-ui#278 · 1 comment ·
All issues in DiamondLightSource/sci-react-ui
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·