Disabling an open Autocomplete still allows option changes
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 62/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- angular, typescript
- Domain
- frontend
Research direction
The bug is in the Autocomplete component's disabled input handling while its option panel is open. Start by finding where disabled is read and where option click handlers emit valueChanged, then check whether the open panel is closed when disabled becomes true. Done when the reproduction steps leave the value at Apple, close the options, and fire no valueChanged event, with a test that toggles disabled while the panel is open.
Written by the indexing model from the issue text.
Description
Reproduction
- Render the Autocomplete with Apple selected and open its options.
- Set the control's
disabledinput to true while the options are open. - Click Orange in the list.
Expected behavior
The options close, the value stays Apple, and no valueChanged event fires.
Actual behavior
The options stay interactive. Clicking Orange changes the value and fires an event.
Reproduced in Chrome 157 on master at aa80e58.
- Dominant language
- TypeScript
- Stars
- 9
- Forks
- 8
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 25
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 AbsaOSS/cps-shared-ui
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
AbsaOSS/cps-shared-ui#948 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
AbsaOSS/cps-shared-ui#875 ·
Maintainers usually reply within 1 day
-
InputComponent - expand type beyond text/number/passwordMay be free again A pull request for this issue was closed without being merged. Openenhancement library
Difficulty 1/5 Under an hour Newbie friendliness 85/100
AbsaOSS/cps-shared-ui#644 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 35/100
AbsaOSS/cps-shared-ui#951 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 Half a day Newbie friendliness 55/100
AbsaOSS/cps-shared-ui#949 ·
Maintainers usually reply within 1 day
All issues in AbsaOSS/cps-shared-ui
Similar issues
-
normalizePropName strips `#` characters from Figma property names instead of only the `#id` suffixOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
figma/code-connect#419 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
jeanibarz/knowledge-base-mcp-server#1268 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Koenkk/zigbee-herdsman-converters#13820 ·
Maintainers usually reply within 2 days
-
A live recovery copy treats a large whole number and text with the same digits as the same valueOpenbug sharing & sync
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day