That is because HTML time input fields depend on the system locale – on my systems set to use a 24 hour clock, it works properly. Guess I should replace them with plain text fields so they work the same regardless of how the user’s computer is configured.
I’ve created an issue on GitHub:
opened 08:00AM - 08 Jul 25 UTC
Time input fields are problematic when entering UTC times, as they may appear as… AM/PM if the browser's locale is set to use 12-hour mode, and there is no way to override that in the application. So it is probably better to replace them with plain text fields (with input validation) so they work the same regardless of browser locale.
See also:
Tried to set up a certain time to monitor some specific calls or areas. It seemed to promote “AM” and “PM”, but yet specifies Zulu time. Only when I exited out did it show Zulu. Might it be better to keep Zulu consistent throughout as the AM/ PM is confusing and not correlating with Zulu anyway?
Hi.
Time filter set form 2200 - 0700 (should ditch the AM / PM thing when setting the time and make it 24 hour for UTC)
Day of the week set to Saturday and Sunday.
What I’d like to know is - does the day of the week activate on the start of the filter time or the end of the filter time? Or will this get ugly crossing over 0000 UTC?