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
When manually typing in either a date to the date time widgets in chrome (116.0.5845.188 or 117.0.5938.89 but this has been around in earlier versions too) the browser will reset and lose the value in the time widget. The opposite also happens in that, if you type in a time in the time widget, then your previously entered date will be reset and lost. e.g.
Typed in a date to the date widget:
Then typing in a time to the time widget and the date widget gets reset: and my previously entered date is lost:
This is a bit frustrating for power users who don't use the click helpers.
Doesn't seem to happen with firefox.
The text was updated successfully, but these errors were encountered:
patching it as a React 18 tss component (convert to a class component as a transitionary step) or refactoring? Brendon will look into properly refactoring because it's a popular component/used in many places
When manually typing in either a date to the date time widgets in chrome (116.0.5845.188 or 117.0.5938.89 but this has been around in earlier versions too) the browser will reset and lose the value in the time widget. The opposite also happens in that, if you type in a time in the time widget, then your previously entered date will be reset and lost. e.g.
Typed in a date to the date widget:
Then typing in a time to the time widget and the date widget gets reset: and my previously entered date is lost:
This is a bit frustrating for power users who don't use the click helpers.
Doesn't seem to happen with firefox.
The text was updated successfully, but these errors were encountered: