Re: [xsl] all-XSLT implementation of Minesweeper

[Sean Whalen <seanwhalen@xxxxxxxxxxx>]

thanks for the feedback.

regarding speed, the performance seem to benefit when I changed 2 
expressions from "//square" to "SweeperMap/square".  But the 
performances varies a lot by how much free space there is on the map.  
The more empty space, the slower the algorythm.  I submitted a bug to 
Mozilla with a sparse map file that shows a big difference between IE & FF:

https://bugzilla.mozilla.org/show_bug.cgi?id=284708

and, regarding DOM mixing, well, yes, and it is worse than mere bad 
form...  Microsoft has a knowledge-base article saying it might throw 
errors:
http://support.microsoft.com/default.aspx?scid=kb;en-us;284856
which I think I saw while coding and testing. 

Sean