4 ms·
200 ms to be precise, definitely feature (a reasonable one) and not a bug (: card.js confirms: if (isFlippable && Date.now() - starttime < 200) { // f
by throwbadubadu 4y ago
200 ms to be precise, definitely feature (a reasonable one) and not a bug (:
card.js confirms:
if (isFlippable && Date.now() - starttime < 200) {
// flip sides
- bscphil 4y agoI don't think that confirms this is not a bug. It's a function that runs on the `mouseup` event, so it's presumably intended to activate on clicks that last less than 200 ms (anything longer is considered a click and drag). This issue triggers as a result of unexpected behavior - a click and drag that lasts less than 200 ms.
- 8n4vidtmkvmk 4y agowhenever i implement 'click' i always check that the final pos of the mouse is within a few pixels of the starting position.
- pkstn 4y agoThat is better way to do it, i should fix it
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]