They're XHR'ing the chart's values based on the user-selected dates. In Chrome, they load ``` https://alertdata.valleywater.org/sensorData/4007/range/2023-01-01/2023-01-11?includeRating=true&skipZeroValues=true ``` but in Firefox, the same selected date range results in ``` https://alertdata.valleywater.org/sensorData/4007/range/1/1/2023/1/11/2023?includeRating=true&skipZeroValues=true ``` I also noticed that something else is off. The default select values are `05/01/2023` and `12/01/2023`, so it looks like the site is expecting `dd/mm/yyyy`. However, opening the date picker in Firefox and Chrome Canary ends up showing me May 2023 and December 2023 respectively. Changing those dates to `01/01/2023` and `01/11/2023` (so, `dd/mm/yyyy`) makes it work. But even Chrome Canary then tries to load the URL with the slashes - so yeah, this indeed looks like another ICU regression. ni?'ing myself to check the JS they're using to pre-populate the date fields, and the JS they're using to generate the URLs.
Bug 1809911 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
They're XHR'ing the chart's values based on the user-selected dates. In Chrome, they load ``` https://alertdata.valleywater.org/sensorData/4007/range/2023-01-01/2023-01-11?includeRating=true&skipZeroValues=true ``` but in Firefox, the same selected date range results in ``` https://alertdata.valleywater.org/sensorData/4007/range/1/1/2023/1/11/2023?includeRating=true&skipZeroValues=true ``` I also noticed that something else is off. The default select values are `05/01/2023` and `12/01/2023`, so it looks like the site is expecting `dd/mm/yyyy`. However, opening the date picker in Firefox and Chrome Canary ends up showing me May 2023 and December 2023 respectively. Changing those dates to `01/01/2023` and `01/11/2023` (so, `mm/dd/yyyy`) makes it work. But even Chrome Canary then tries to load the URL with the slashes - so yeah, this indeed looks like another ICU regression. ni?'ing myself to check the JS they're using to pre-populate the date fields, and the JS they're using to generate the URLs.