Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Inputs should have explicit `readonly` styling

Open
#620 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Domain
design

Research direction

Start from the issue description and inspect how inputs currently handle the readonly attribute and selected states. Determine the project’s existing styling conventions for readonly inputs, then verify that readonly controls have explicit styling and do not show inappropriate selected states.

Written by the indexing model from the issue text.

Description

enhancement

We're currently ignoring the readonly attribute and any styling. At the very least, we should probably turn off selected states here?

Dominant language
TypeScript
Stars
672
Forks
107
Avg merge
2d 12h
Merged PRs (30d)
26

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 StackExchange/Stacks

All issues in StackExchange/Stacks

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.