Files
frigate/web/src
Josh Hawkins 9c1fb2e5e9 recording timestamp fix
when startTime is exactly on an hour boundary, findIndex returns the first matching chunk, which is the previous hour's chunk (where before == startTime), instead of the correct chunk (where after == startTime)

the bug shows up when using the share timestamp feature and sharing a specific timestamp on the exact hour mark. when accessing the shared link, the timeline would jump to the incorrect hour
2026-05-01 10:20:43 -05:00
..
2026-04-30 17:19:53 -06:00
2026-04-18 07:10:50 -06:00
2026-04-03 17:46:43 -05:00
2026-04-26 17:09:35 -05:00
2026-05-01 10:20:43 -05:00
2026-03-07 06:43:00 -07:00
2024-02-28 16:23:56 -06:00
2025-02-10 09:42:35 -07:00
2022-03-11 07:49:06 -06:00