You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Interact with Standard integer with formatting field as follows:
Unfocus the field.
Observe the value is 1,500,000.
Click between the comma and the hundreds place.
Observe that when the input field switches to edit mode, the cursor blinks between the hundreds and tens place.
On same page and Standard integer with formatting field:
Unfocus the field.
Observe the value is 1,500,000.
Attempt to select/highlight 500 by click-dragging the mouse.
Observe that the selection highlight in the focused field (edit mode) starts after the 5.
Possible Solution
Not sure how to fix this. Maybe this way?
When user clicks on formatted field,
determine location of cursor in formatted value,
map location of cursor to unformatted value. something like...
1 , 5 0 0 , 0 0 0 formatted value
│ └─┤ │ │ ├─┘ │ │ │
└─┐ │ │ │ │ ┌─┘ │ │
│ │ │ │ │ │ ┌─┘ │
│ │ │ │ │ │ │ ┌─┘
1 5 0 0 0 0 0 unformatted value (edit mode)
each side of a comma would map to the same edit-mode cursor location.
And something similar with the selection issue, though I imagine if the cursor starts at the correct position in edit mode kicks in, then dragging the selection highlight would Just Work™ without further effort.
The text was updated successfully, but these errors were encountered:
I was hoping to avoid using any Range and Selection API, but it seems like we need to use them. I will try and work on it sometime soon, thanks for reporting this issue.
Steps to reproduce:
On same page and Standard integer with formatting field:
Possible Solution
Not sure how to fix this. Maybe this way?
And something similar with the selection issue, though I imagine if the cursor starts at the correct position in edit mode kicks in, then dragging the selection highlight would Just Work™ without further effort.
The text was updated successfully, but these errors were encountered: