Still playing around with this. Works in all Gecko browsers (Firefox etc).

Opera 9 and Konqueror 3.5.2 have repaint issues.

(repaint worked around, and a Konqueror/Safari colgroup bug)

Gecko browsers occasionally position pieces incorrectly after "reset" button (overlapping two ranks). Appears to be font size dependant (not reproducible consistently through all CTRL +/CTRL -). Also the new reflow refactor seems to have fixed this in Firefox 3.0/Seamonkey 1.5

IE6 and IE7 seem to be confused by concepts like onmousedown and "unicode"

Mostly just fun referencing chess pieces in code. Working on a basic client/server now... Using text requires a font with support for unicode Symbol, Other in the range of 9812-9823. Kass' awesome Code 200x complete unicode. A non-unicode version

White Black
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
a b c d e f g h
8 8
7 7
6 . . . . . . . . 6
5 . . . . . . . . 5
4 . . . . . . . . 4
3 . . . . . . . . 3
2 2
1 1
a b c d e f g h

Seconds per move

Still missing SAN parsing (that will be rather extensive) and error in keeping track of captures for stepping backwards. This may be in part due to having taken a toy and tacking on to it. Keeping track of state wasn't as important before. At this point, wondering if I shouldn't have the board keep better track of where all the pieces are... If comments are used, assumption is each move will start on a new line. Attempts to make your own moves during playback may lead to unpredictable results. It might be interesting to try to weave those into the game later. Chess notation being semi annoying to parse, right now spaces in moves are disallowed (e2-e4 not e2 - e4) and only one space between white and black move. Need to consider making a better parser.