Problem: at large scales (1:1000 for instance) in Mozilla-based browsers, the
map becomes 'sticky' and won't pan properly in the horizontal and/or vertical
dimension.  It seems dependent on the map file.

Analysis: ka-Map uses some simple math to determine pixel locations by assuming
they are relative to the origin of the projection.  In theory, this should be
fine as browsers support very large numbers in javascript.  These pixel offsets
are used to absolutely position the images in a div that is then offset by an
opposite amount to make the image visible.  This works great for pixel locations
up to 1 million.  After this, the style object in mozilla converts the numbers
to scientific notation with a fixed number of decimal places, effectively
rounding or truncating the numbers.  The result is that between 1 million and 10
million in pixel coordinates, the style object rounds the last digit.  Between
10 million and 100 million, it rounds two places ... meaning that a single mouse
event must cover 100 pixels to trigger movement.

Solution: convert all calculations to a floating origin so that image offsets
never get very large.  Unfortunately, this will affect loads of code.