lichess.org
Donate

New puzzle format

It doesn't work for me still, I suspect the hard refresh was what did it for Leeness
Are the problem/puzzle positions taken from Lichess games?
I got it fixed. I made a new firefox profile by running /usr/bin/iceweasel -no-remote -P, then creating a new profile. Voila, puzzle trainer suddenly worked. What's different? I copied over the prefs.js file (the file which contains the about:config settings for firefox, or something like that) to the new profile that was created, and now it didn't work anymore. So the culprit probably resides in prefs.js. I resetted settings until the puzzle started working, and I pinned it down to the setting `dom.w3c_touch_events.enabled`. I have, for some reason or other set it to the integer 1 (I can't remember why, but I think I was fixing something, unless I'm recalling some other unrelated setting), when I reset it to the integer 0, it works. 0 means 'disable', I presume, so I have no idea how that's supposed to help with this, but it did.

So the question is, are there actually good reasons for having `dom.w3c_touch_events.enabled` set to 1? I have no idea.

The board editor also worked.

~*~ FinkelFrand out ~*~
Btw, for anyone experiencing the same with firefox, here's how I fixed it:

* enter 'about:config' in the adress bar
* then, on the page that appears, write 'dom.w3c' into the search bar
* One of the settings you see has the name `dom.w3c_touch_events.enabled`. Make sure its value is the integer 0.

I experienced the same problem on chromium 37, by going to 'about:flags' and enabling the setting with this description:
>Enable touch events Mac, Windows, Linux, Chrome OS
>Force touchscreen support to always be enabled or disabled, or to be enabled when a touchscreen is detected on startup (Automatic, the default). #touch-events

Then I changed that it to 'disable' and the puzzle worked again. The default option for that setting is 'automatic', so maybe @Leeness for some reason the automatic choice for you is 'enable' and that's the problem (maybe your hardware has support for touch features or something). Setting it to 'disable' might be worth a shot (you have to restart the browser afterwards for the change to take effect).
Probably has something to do with the fact that Chessground is designed to work on both mouse and touch devices (for the upcoming mobile app).

This topic has been archived and can no longer be replied to.