Hi Rikki, good question. It was regular desktop Google Chrome (version 157) on Windows 11, not a special preview browser. My script drives it through Chrome's normal debugging connection, so it's the same browser engine players get. The game window was small, though (about 1100x550).
How that affects each note:
1. The video errors are the one most likely to hit real players. The file is a QuickTime .mov, and Chrome failed to decode it on every load I did. Safari plays .mov natively, so if you tested there you probably never saw it. Firefox and Edge will likely behave like Chrome. Re-exporting that clip as .mp4 (H.264) or .webm should fix it everywhere.
2. and 3. (the power clock running while the POWER CRITICAL card waits, and the item jumping to the cursor) are game logic, so the browser shouldn't change them. But my clicks were scripted, so #3 may partly be my aim. A quick human try would confirm it either way.