since a few days i am facing a graphics error: sometimes, when opponent takes one of my pieces, say my pawn with a knight , my pawn disappears but the knight is still on the square it came from. this only happens when pieces are taken. only when i move another piece over that original square, the knight shows up its correct square.
OS.X 10.7 , firefox 48.0.2.
I've witnessed a similar issue three times in four games when premoving: if the opponent takes one of my pieces and I 'premove' the takeback, the opponent's piece still sits at its original square. As if the premove is rendered before the opponent's move it reacted to.
I only witnessed this in Firefox 47.0 - never happened in Chrome. OS is Ubuntu 15.10.
I agree, it happens when I premove a takeback. opponents piece still visable on its original square. When I drag one of my pieces over that piece (like a pencil in photoshop) I can erase it like in a painting program.
"When I drag one of my pieces over that piece (like a pencil in photoshop) I can erase it like in a painting program"
Ok, so it's definitely a Firefox rendering bug. Oh boy.
Can you make it happen every time?
Not sure every single time, but at least very often when premoving. Maybe a concrete instance of the issue will help you track it down: in game
en.lichess.org/lXggCcTWPNtA, after 17. Nxe5 dxe5, the white knight was still on f3.
I just tried it with the DOM-inspector on and selected the div with class 'cg-board'. I had three pre-move recaptures, but the issue didn't happen once!
i checked out a few games:
i face it just in bullet games!
happens to me on most of the premove recaptures.
in blitz or longer games seems it doesnt happen.
just opponents pieces "affected", never mine
Based on pumskins' findings I tested with Firefox developer tools opened, but this time with a bullet game. The issue did occur again. The entries in the cg-board-div were updated correctly, but the piece wasn't removed from the screen.
"I can only reproduce it on Fx 47 & 48." Thibault
Means it wont be fixed?
But yes, the error does not occur on FX 42 .
Firefox 48 is the latest version under OSX 10.7 which is the latest OS running an Intel Core 2 Duo. Bad luck.
