-
Notifications
You must be signed in to change notification settings - Fork 555
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mixed TZ in live blog #26977
Comments
Hi, thank you for raising this. From your screenshots it looks like you can see TX from 3 different editions (Europe, US, and UK), which shouldn't happen. Would you be able to share a link to an affected liveblog and let us know which Guardian edition you're using? Could you also let us know whether you switched editions (from the top nav menu) while reading this liveblog? As we haven't received any other reports of this yet, we will look into it further if we are able to recreate this or if it gets reported again. |
My first screenshot is from the 19 March 2024 UA live blog. The second is from the Krokus attack live blog on 22 March. When I look back at them now, both display TZ consistently as CET, and the conversions GMT->CET and EDT->CET are correct. These days I am always on the Europe edition with some extremely rare (twice or thrice per year) exceptions. I had not switched editions on the dates of the TZ mixups, nor in the preceding days. All my cookies get cleared when I close my browser, so a cookie-related mix-up of editions is very unlikely. Finally, today's UA live blog shows timestamps consistently in CEST. And if I switch editions, consistently in AEST, BST or EDT respectively. Dunno, perhaps those days in March the PFY was in the basement having fun? |
Please see the attached screenshot from today's live UA blog. The latest entry is at 09:51 GMT, the previous one is at 10:39 CET. The time zone used to be consistent, but it has been like this for a few months now. Note: I am neither in GMT nor CET, so in case you're trying to display the time dynamically by geolocation, it's not working.
The text was updated successfully, but these errors were encountered: