jamespandClaude Opus 5
0703699929
The theme gives every button a pressed effect -- button:active sets position: relative; top: 1px. Splide renders its arrows as <button>, so they matched it and flipped from absolute to relative positioning for as long as the mouse was held down, jumping 181px out of their centred position mid-click. mousedown and mouseup therefore landed on different elements (the arrow, then the caption overlay behind it), so the browser fired click on their common ancestor and the arrow's own handler never ran. Nothing was logged because nothing errored. Restoring absolute positioning for .splide__arrow:active fixes it. Autoplay and the pagination dots were unaffected throughout, which is why this looked like the arrows specifically were unbound -- they were bound, the click just never reached them. Verified with real mouse clicks (not synthetic .click(), which bypasses hit-testing and masked the bug) on both sites. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>