-
Notifications
You must be signed in to change notification settings - Fork 1.4k
fix: various S2 bug fixes from docs testing #9272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
1d99290
3f41d87
fb9e7e5
513a9f9
49c488d
8c2b0fc
62171d0
0de2963
aca98d3
c0e7f6f
8744470
207bb26
2f7943d
2d7cd50
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -202,7 +202,8 @@ export const FieldGroup = forwardRef(function FieldGroup(props: FieldGroupProps, | |
| } | ||
| }} | ||
| onTouchEnd={e => { | ||
| if (!(e.target as Element).closest('button,input,textarea,[role="button"]')) { | ||
| let target = e.target as HTMLElement; | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. test for this change?
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I added a test for textarea, but couldn't get the datepicker test to quite simulate the proper touch end event on the content editable for some reason... Using user event doesn't trigger the touchEnd properly and firing events on the spinbuttons directly doesn't seem to work either |
||
| if (!target.isContentEditable && !target.closest('button,input,textarea,[role="button"]')) { | ||
| e.preventDefault(); | ||
| (e.currentTarget.querySelector('input, textarea') as HTMLElement)?.focus(); | ||
| } | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
behavior open to debate, but the single select calendar case had a prior test for it hence why the special casing. I think this makes sense, range calendars don't actually include unavailable days that fall inside their range selection, but a single select calendar might have a value/default value set that is invalid + unavailable