It seems like they're getting what they asked for, people are posting a bunch of bugs.
My personal pain point was when I figured out that Safari supports only a subset of the Date format standard (RFC which is a part of an ISO or something like that, basically there are some dates that only Safari can't parse).
Now it's up to them to live up to the purpose of the thread, if it means anything.
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.
Dates are weird in JS/browsers so I wouldn't be at all surprised if some browser was strictly adhering to a standard, and the other browser... also strictly adhering to a standard, but a different one. Or both being lax. Or one of them being lax. Or...
