Skip to content
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

ResponsiveTimerange rendering inconsistency on Safari #2519

Open
tabishnaqvi1311 opened this issue Feb 26, 2024 · 0 comments
Open

ResponsiveTimerange rendering inconsistency on Safari #2519

tabishnaqvi1311 opened this issue Feb 26, 2024 · 0 comments

Comments

@tabishnaqvi1311
Copy link

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:

  1. Initiate a new responsive timerange
  2. Add the start date = 2024-1-1 and the end date = 2024-06-30 (or 2024-06-30)
  3. Open the same window in Chrome and Safari
  4. 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
Screenshot 2024-02-26 at 10 09 24 PM
Brave
Screenshot 2024-02-26 at 10 09 41 PM

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant