-
-
Notifications
You must be signed in to change notification settings - Fork 449
Open
Labels
Status: TriageThis is the initial status for an issue that requires triage.This is the initial status for an issue that requires triage.invalidThis doesn't seem rightThis doesn't seem right🐛 BugIndicates that the issue is a bug or defect.Indicates that the issue is a bug or defect.
Description
Describe the bug
The Community Calendar events list is failing to sort chronologically for users on Safari and iOS devices.
Currently, calendarUtils.ts formats dates as YYYY-MM-DD HH:mm:ss (e.g., 2024-10-15 14:30:00) before passing them into new Date() for sorting. This format is not strictly ISO 8601 compliant because it lacks the T separator.
While V8 browsers (Chrome, Edge) are forgiving and parse this correctly, WebKit (Safari/iOS) strictly follows the spec and evaluates new Date('2024-10-15 14:30:00') as NaN. This causes the array .sort() to fail, leaving the events list completely unsorted for Apple users.
Steps To Reproduce
- Open the JSON Schema community/events page on Safari (macOS or any browser on iOS).
- Notice that the upcoming events are not sorted chronologically.
- Open the Safari console and run
new Date('2024-10-15 14:30:00').getTime(). Observe that it returnsNaN.
Expected Behavior
Events should be listed in chronological order across all modern browsers.
Screenshots
No response
Device Information [optional]
- OS:
- Browser:
- version:Are you working on this issue?
Yes
Do you think this work might require an [Architectural Decision Record (ADR)]? (significant or noteworthy)
Yes
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Status: TriageThis is the initial status for an issue that requires triage.This is the initial status for an issue that requires triage.invalidThis doesn't seem rightThis doesn't seem right🐛 BugIndicates that the issue is a bug or defect.Indicates that the issue is a bug or defect.