Windows 10 reached EOS (end of support) on October 14, 2025. For more information, see this article.

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Problems with timing?

  • 1 个回答
  • 0 人有此问题
  • 81 次查看
  • 最后回复者为 cor-el

Ok, so this is an odd one.

I gamble with William Hill online using Firefox as my browser.

Every year this same problems happen when the clocks go forward in spring time here in the UK.

So I go on the WH website Sunday (for example) at 11pm and it will show me Mondays football matches. But. At 12am Monday until 1am, the now todays football matches do not appear. Its like the browser can no accept this time period exists because as soon as 1am comes, the matches (for Monday) appear.

So I contacted WH for support. They advised that if I am using Firefox that I should try IE instead. So I did. And guess what? The problem doesn't happen on IE. Mondays matches do exist between 12am and 1am. So it is definitely a firefox issue.

But the issue resolves at the end of October when the clocks go back.

So what is going on here? Any solutions? This has been going on several years.

Ok, so this is an odd one. I gamble with William Hill online using Firefox as my browser. Every year this same problems happen when the clocks go forward in spring time here in the UK. So I go on the WH website Sunday (for example) at 11pm and it will show me Mondays football matches. But. At 12am Monday until 1am, the now todays football matches do not appear. Its like the browser can no accept this time period exists because as soon as 1am comes, the matches (for Monday) appear. So I contacted WH for support. They advised that if I am using Firefox that I should try IE instead. So I did. And guess what? The problem doesn't happen on IE. Mondays matches do exist between 12am and 1am. So it is definitely a firefox issue. But the issue resolves at the end of October when the clocks go back. So what is going on here? Any solutions? This has been going on several years.

所有回复 (1)

What time is reported if you paste these code one at the time in the Web Console ?

  • (new Date()).toLocaleString()
  • (new Date()).toLocaleString("en-US",{weekday:"long",day:"numeric",month:"long",year:"numeric",hour:"numeric",minute:"numeric",second:"numeric",hour12:true,timeZoneName:"short"});
  • (new Date()).toLocaleString("en-US",{weekday:"long",day:"numeric",month:"long",year:"numeric",hour:"numeric",minute:"numeric",second:"numeric",hour12:false,timeZoneName:"short"});