cm-chessboard 8.12.5 → 8.12.7

package/README.md

@@ -289,6 +289,10 @@ chessboard-sprite-staunty.svg) and a sprite of the
 Sprites must be 40x40px in size where the piece elements must have ids like
 "bp" (black pawn) or "wq" (white queen). Just open the sprite in a text editor, SVG is readable like HTML.
 
+### More piece sets
+
+[piece-packager](https://github.com/deverac/piece-packager) by @deverac ships 80+ prepackaged piece sets ready to drop into `assets/pieces/`, plus a tool to bundle your own 12 individual piece files (SVG or PNG) into a cm-chessboard-compatible sprite.
+
 ## Extensions
 
 cm-chessboard provides the ability to extend its functionality with extensions. Extensions extend the class `Extension`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cm-chessboard",
-  "version": "8.12.5",
+  "version": "8.12.7",
   "description": "A JavaScript chessboard which is lightweight, ES6 module based, responsive, SVG rendered and without dependencies.",
   "keywords": [
     "chess",

package/src/view/PositionAnimationsQueue.js

@@ -246,7 +246,10 @@ export class PositionAnimationsQueue extends PromiseQueue {
 
     async enqueuePositionChange(positionFrom, positionTo, animated) {
         if(positionFrom.getFen() === positionTo.getFen()) {
-            return Promise.resolve()
+            // No diff to animate. Still go through the queue so the promise
+            // resolves after any animations already in flight (e.g. an
+            // earlier movePiece from a drag). See issue #154.
+            return super.enqueue(() => Promise.resolve())
         } else {
             return super.enqueue(() => new Promise((resolve) => {
                 let duration = animated ? this.chessboard.props.style.animationDuration : 0

package/test/TestChessboard.js

@@ -69,6 +69,36 @@ describe("TestChessboard", () => {
         chessboard.destroy()
     })
 
+    // Regression for https://github.com/shaack/cm-chessboard/issues/154
+    //
+    // A setPosition() call with a null diff (positionFrom === positionTo)
+    // used to bypass the animation queue entirely and resolve on the next
+    // microtask. That's wrong when an earlier animation — here the animated
+    // movePiece — is still in the queue: the setPosition promise must wait
+    // for that to drain before resolving, otherwise callers following the
+    // "await setPosition(...); then continue" pattern run their
+    // continuation before the board is visually settled.
+    it("setPosition should wait for pending animations even on a null diff (#154)", async () => {
+        const chessboard = new Chessboard(document.getElementById("TestPosition"), {
+            assetsUrl: "../assets/",
+            position: FEN.start,
+            style: {animationDuration: 100}
+        })
+        let movePieceResolved = false
+        const movePromise = chessboard.movePiece("e2", "e4", true).then(() => {
+            movePieceResolved = true
+        })
+        // Same FEN as the position after movePiece → null diff inside
+        // setPosition. The animated movePiece above is still queued.
+        const targetFen = "rnbqkbnr/pppppppp/8/8/4P3/8/PPPP1PPP/RNBQKBNR"
+        const setPromise = chessboard.setPosition(targetFen, true).then(() => {
+            assert.equal(movePieceResolved, true,
+                "setPosition resolved before the pending movePiece animation finished")
+        })
+        await Promise.all([movePromise, setPromise])
+        chessboard.destroy()
+    })
+
     // Regression for a production crash: the ResizeObserver callback defers
     // handleResize() via setTimeout to avoid "ResizeObserver loop completed"
     // warnings. If destroy() is called between the observer firing and the