Determine if we should offer or deprecate focusTrapDisabled
prop for input-date-picker
and input-time-picker
#10690
Labels
0 - new
New issues that need assignment.
needs triage
Planning workflow - pending design/dev review.
spike
Issues that need quick investigations for time estimations, prioritization, or a quick assessment.
Background
This is a follow-up issue to serve as a reminder that we need to determine next steps for
input-date-picker
andinput-time-picker
with regards to offering the ability to disable focusTrap.input-date-picker
/input-time-picker
currently offersfocusTrapDisabled
and it could make sense depending on what the user is implementing in their workflows.One suggestion is (@driskull) to deprecate
focusTrapDisabled
at some point in the future and have these components no longer support any focus trapping. They should act like a single component and be controlled via arrow keys only so tabbing past them is easier for an end user.We need to collect feedback from teams from now until 4.x to helps us make a better call.
Relevant Issues/PRs: #10578 #8982 #10685
Desired Outcome
Determine if we should offer or deprecate
focusTrapDisabled
prop forinput-date-picker
andinput-time-picker
.The text was updated successfully, but these errors were encountered: