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
Describe/explain the bug
I used the Responsive Timerange component and noticed an inconsistency in the way that it renders on different browsers due to flexibility in the date format passed in the "from" and "to" props. The components collapses in Safari, but renders in chromium based browsers such as Chrome and Brave.
To Reproduce
Steps to reproduce the behavior:
Initiate a new responsive timerange
Add the start date = 2024-1-1 and the end date = 2024-06-30 (or 2024-06-30)
Open the same window in Chrome and Safari
Notice how it collapses in safari, but renders without any message or warning on Chrome
Expected behavior
Provide a way for develper to know inputted dates are incorrectly formatted on all browsers, through a message in the console, etc, instead of the developer having to tackle this inconsistency later.
Screenshots
Safari
Brave
Desktop (please complete the following information):
OS: MacOS
Browser: Chrome, Safari
Safari Version 17.1 , Brave Version 1.62.165
Also thanks for creating such an elegant component!
The text was updated successfully, but these errors were encountered:
Describe/explain the bug
I used the Responsive Timerange component and noticed an inconsistency in the way that it renders on different browsers due to flexibility in the date format passed in the "from" and "to" props. The components collapses in Safari, but renders in chromium based browsers such as Chrome and Brave.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Provide a way for develper to know inputted dates are incorrectly formatted on all browsers, through a message in the console, etc, instead of the developer having to tackle this inconsistency later.
Screenshots
Safari
Brave
Desktop (please complete the following information):
Also thanks for creating such an elegant component!
The text was updated successfully, but these errors were encountered: