Safari handles parsing dates differently than other browsers. Here is one way of fixing it by handling the date as a string before making it a Date object
I think you can also maybe using something like date-fns to handle the cross platform behavior for parsing dates (although I personally think that might be too overkill for just this one use case)
Test Plan
Verified that the result is the same as what's on prod. Tested on Mac and iOS
Summary
Safari handles parsing dates differently than other browsers. Here is one way of fixing it by handling the date as a string before making it a Date object
I think you can also maybe using something like
date-fns
to handle the cross platform behavior for parsing dates (although I personally think that might be too overkill for just this one use case)Test Plan
Verified that the result is the same as what's on prod. Tested on Mac and iOS
Issues
Closes #947