ni / ni/nimble

Read-only / readonly text field and number field do not have focus states

Open
#2,879 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
39
Forks
14
Avg merge
1d 16h
Merged PRs (30d)
13

Description

🐛 Bug Report

The read-only state of the nimble-text-field and the nimble-number-field are focusable (which is correct), but there is a clear focus-visible state. When there is text in the input, the text becomes highlighted when the control gets focus, but when the value is empty, there is no visual indication that the control is focused.

💻 Repro or Code Sample

🤔 Expected Behavior

When the nimble-text-field or nimble-number-field is read-only and focused, there should be a clear visual indication that the control is focused.

😯 Current Behavior

The only indication that a read-only nimble-text-field or a read-only nimble-number-field has focus is that the text within it gets highlighted. However, this is not enough of an indication that the field is focused, particularly when the text field is empty.

💁 Possible Solution

🔦 Context

Currently tabbing to a read-only text field makes it looks like focus becomes lost on the page.

🌍 Your Environment

  • OS & Device: [e.g. MacOS, iOS, Windows, Linux] on [iPhone 7, PC]
  • Browser [e.g. Microsoft Edge, Google Chrome, Apple Safari, Mozilla FireFox]
  • Version [e.g. 1.8.0]

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.

Research direction

Locate the nimble-text-field and nimble-number-field entry points and their focus-state tests or styles. Reproduce the issue by tabbing to each empty, read-only field, then verify that both show a clear visual focus indication without relying on selected text.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
accessibility, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.