That’s a bug worth reporting to them on Twitter! Which dates, incidentally?
I just tried it in my Safari and it seems to give you an "Invalid Date" which it doesn't in Chrome.
Not sure if it's a bug, maybe a design choice. Anyway, in my case I received dates from a backend and was supposed to visualize a chart with them and some supplementary data, so I had to parse them and at some point we learned that the chart was broken for users in Safari because they'd get "Invalid Date" after parsing.
Browsers are a mess, frankly :)