Code of conduct
Impacted component(s)
sp-number-field
Library version
1.10.0
Expected behavior
When entering input into an sp-number-field, an IME user should be able to use the arrow keys to freely move between various options (including conversion between double-byte and single-byte encodings) before committing.
Actual behavior
Instead of allowing the user to move freely between IME options, the popup immediately closes when an item with non-Arabic digits is highlighted and the old value is restored.
This occurs in Express, Squirrel, and on the Storybook.
Screenshots
No response
What browsers are you seeing the problem in?
Chrome
How can we reproduce this issue?
- Go to the
sp-number-field Storybook
- Ensure a Japanese keyboard is enabled
- Click on the number field shown under "Enter a number"
- Begin typing a number (e.g. 800) - it will initially render using double-byte characters (e.g. 800)
- Press down arrow to open the IME window; this allows users to choose between different ways of writing the number in Japanese.
- Using the arrow keys, highlight an item with non-Arabic numerals (e.g. 八〇〇)
- Note that the IME window immediately closes and the new value is lost
Sample code or abstract reproduction which illustrates the problem
No response
Severity
SEV 3
Logs taken while reproducing problem
No response
Would you like to track this issue in Jira?
Code of conduct
Impacted component(s)
sp-number-field
Library version
1.10.0
Expected behavior
When entering input into an
sp-number-field, an IME user should be able to use the arrow keys to freely move between various options (including conversion between double-byte and single-byte encodings) before committing.Actual behavior
Instead of allowing the user to move freely between IME options, the popup immediately closes when an item with non-Arabic digits is highlighted and the old value is restored.
This occurs in Express, Squirrel, and on the Storybook.
Screenshots
No response
What browsers are you seeing the problem in?
Chrome
How can we reproduce this issue?
sp-number-fieldStorybookSample code or abstract reproduction which illustrates the problem
No response
Severity
SEV 3
Logs taken while reproducing problem
No response
Would you like to track this issue in Jira?