[DateRangePicker] Using SingleInputDateRangeField with readOnly=true causes unexpected UX

[TimESQuit]

[DateRangePicker] Using SingleInputDateRangeField with readOnly=true causes unexpected UX

[LukasTy]

I can't fully tell, but does the code fix just apply to v7? We recently migrated to v6 and are not looking to migrate to v7 right away so would really need this change in v6 as well. Thanks!

It has been fixed only on v7 for now.
We'll backport the fix to v6 as well. 👌

[LukasTy]

@TimESQuit The problem has been identified and a possible fix PR raised.
I've also noticed that the focused flag has not been properly added to the SingleInputDateRangeField—it does not receive focus style when focused, only when Picker is opened.

P.S. If you would try adding an enableAccessibleFieldDOMStructure prop—the UX behavior would work as expected even on v7.0.0.
Feel free to try these new Field components if you have the option. 😉

[TimESQuit]

Around next Thursday works. Thanks!

[michelengelen]

Hey @TimESQuit your Codesandbox is unavailable. You might have to make it public.
Could you do that and comment here when it is available so we can have a look? Thanks!

[TimESQuit]

@michelengelen
Sorry about that - should be public now

[github-actions]

⚠️ This issue has been closed.
If you have a similar problem, please open a new issue and provide details about your specific problem.
If you can provide additional information related to this topic that could help future readers, please feel free to leave a comment.

How did we do @TimESQuit?
Your experience with our support team matters to us. If you have a moment, please share your thoughts through our brief survey.

[TimESQuit]

I can't fully tell, but does the code fix just apply to v7? We recently migrated to v6 and are not looking to migrate to v7 right away so would really need this change in v6 as well. Thanks!

[LukasTy]

@TimESQuit Would it be fine if we released this fix on v6 in around a week (~next Thursday)?