Bugzilla

(In reply to André Bargull [:anba] from comment #4)
> We were aware that such bugs might arise, see bug 1792775, comment #16. That's why we timed this change, so it happens at the same time as in Chromium. Can we first try to notify the website owner, so they update their code to handle the new date-time format for `en-US`? If that fails we should consider adding an intervention.

Thanks, I'll try to contact them then and file a bug for an intervention.

There is another report about group pages on meetup.com being broken as well in https://github.com/webcompat/web-bugs/issues/115508. 
They use `toLocaleTimeString` and expecting third element to be present in an array after splitting a string with a space, but it's undefined:

```js
   const t = (new Date).toLocaleTimeString('en-us', {
        timeZone: "US/Mountain",
        timeZoneName: 'short',
        hour12: !0
    }).split(' ') [2]
```

(In reply to André Bargull [:anba] from comment #4)
> We were aware that such bugs might arise, see bug 1792775, comment #16. That's why we timed this change, so it happens at the same time as in Chromium. Can we first try to notify the website owner, so they update their code to handle the new date-time format for `en-US`? If that fails we should consider adding an intervention.

Thanks, I'll try to contact them then and file a bug for an intervention.

There is another report about group pages on meetup.com being broken as well in https://github.com/webcompat/web-bugs/issues/115508. 
They use `toLocaleTimeString` and expecting third element to be present in an array after splitting a string with a space, but it's undefined (since the change in spaces):

```js
   const t = (new Date).toLocaleTimeString('en-us', {
        timeZone: "US/Mountain",
        timeZoneName: 'short',
        hour12: !0
    }).split(' ') [2]
```