![Firefox logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2020-04-14-08-36-13-8dda6f.png)
Wrong behavior on lichess.com.
Foxfire behaves incorrectly when playing chess on lichess.com. This is a popular chess playing site that hosts online chess games between logged in players. When a game challenge is accepted, it presents a chess board and a clock that should start immediately counting down white's remaining time. Instead, with Foxfire, the clock starts when the first move is made by white.
The above behavior only occurs on Foxfire. On Edge, Google Chromium, and Opera, it works correctly. This is of little significance to most players, but I have observed it for a long time on Foxfire--maybe as long a two years. I have not reported it before because I can easily work around the problem. The workaround is obviously to switch away from Foxfire when playing chess on lichess.com.
Just thought someone there ought to know about this Foxfire abnormality.
모든 댓글 (3)
To be honest, this seems like something that should be directed to the Devs of lichess.com primarily...
It sounds like something simple needs to be tweaked within their code, if as I expect the game is runs JS or scripts in general.
Ive tried to reach the site, to observe/recreate the above mentioned behaviour myself (and how its being implemented) but when clicking the link I'm 404-timed out. If it is an endemic issue with the FireFox browser code and how it's handling JS or HTML5 this is likely a niche issue, and would likely be a more impactful report from the devs themselves, if there's nothing wrong their end.
Hope you continue to use the security friendly browser for your other online activities, regardless of the outcome to this.... it maybe the security principles in place within Firefox that's causing this issue, not allowing a script to run until an action is taken maybe... again this is just my own speculation as I've been unable to test it myself.
While I appreciate your attention on this matter, it neither explains nor solves the problem. I am astonished by your inability to reach lichess.com because of a 404-time-out.. It is a very popular site, continually hosting around 50,000 simultaneous chess games. I plan to send this message thread to the lichess.com operators in the hope that they can provide an explanation. I would, of course, be happy to see a resolution from either side.
My apologies! It is lichess.org, not lichess.com. The problem is still there, but I note on searching the lichess.org community site that it has been reported there.