When we view 24hrs, at times, and only on devices (at least iOS), the sorting seems wrong.
The following conditions trigger the problem:
a) You are on a mobile device (iOS, for sure)
b) You have more than 100 events, which means 2 http seeks (each http seek gets 100 events)
c) HTTP 2 is returned before HTTP 1
What happens then is:
a) HTTP2 returns events in sorted order, 101-whatever (API ensures it) but those dates or "older" than HTTP1
b) HTTP1 returns events in sorted order (1-100)
We now have a situation where the 24hr array has older events first, newer events later, both sorted, but within their own values.
We now have a master sort code that sorts the full array on start time. It does this by converting StartTime string to a JS date object first. This works on desktop, fails on devices.
Therefore, when the situation above occurs, desktops are able to rectify, device sorting fails, resulting on old events showing up first.
When we view 24hrs, at times, and only on devices (at least iOS), the sorting seems wrong.
The following conditions trigger the problem:
a) You are on a mobile device (iOS, for sure)
b) You have more than 100 events, which means 2 http seeks (each http seek gets 100 events)
c) HTTP 2 is returned before HTTP 1
What happens then is:
a) HTTP2 returns events in sorted order, 101-whatever (API ensures it) but those dates or "older" than HTTP1
b) HTTP1 returns events in sorted order (1-100)
We now have a situation where the 24hr array has older events first, newer events later, both sorted, but within their own values.
We now have a master sort code that sorts the full array on start time. It does this by converting StartTime string to a JS date object first. This works on desktop, fails on devices.
Therefore, when the situation above occurs, desktops are able to rectify, device sorting fails, resulting on old events showing up first.