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

[SensitiveInput] Description and error messages disappear without a label

Open Beginner friendly
#855 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
react, typescript

Research direction

Read packages/kumo/src/components/sensitive-input/sensitive-input.tsx at the cited condition, then compare how the other inputs render Field. Check both suggested cases: description and error should render without a visible label and retain the usual accessible association. Done when both props display correctly without a label.

Written by the indexing model from the issue text.

Description

The component creates a Field wrapper only when label is truthy. A description or error without a visible label is silently omitted, despite both being supported props.

Suggested reproduction:

<SensitiveInput aria-label="Secret" description="Keep this value private" />
<SensitiveInput aria-label="Secret" error="A value is required" />

The first input should show its description; the second should show its error, with the usual accessible association.

Please render Field when any of label, description or error is provided, matching the other inputs. The current condition is only if (label).

Source review of main at 828866ab5273d2e795a33c6360040a650371406b; this is a suggested reproduction, not a browser-tested report. No matching issue was found in component-name and keyword searches.

Dominant language
TypeScript
Stars
4k
Forks
184
Avg merge
22h 44m
Merged PRs (30d)
52

Getting set up

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 cloudflare/kumo

All issues in cloudflare/kumo

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.