You need to log in before you can comment on or make changes to this bug.
When performing the smoke test on the most recent Beta candidate (2004-05-21), clicking on the keymap image causes the map preview to blank out permanently and also removes any extent markings from the keymap. When trying the same thing in a more adhoc fashion, sometimes the first one or two clicks on the keymap work properly, but eventually it always has the same "blanking" effect. This is a problem on both Windows and Linux.
Set Target Milestone to 1.99 Beta
reproduced. The smoke test steps do not include repetitive clicking on the keymap. Perhaps the smoke test should be updated to ensure that this gets tested (i.e. use the keymap to navigate to several locations consecutively)
working on this now
the problem appears to be the calculation of the bottom and top edges of the map, they are shifted up. The vertical height is maintained correctly, but the top edge is moved way off the top of the map. It is always moved to 34039119 in my example ... horizontal calculations appear correct. Suspect change made previously to correct problem with reflecting in left/bottom of the image ...
oopps, can't be that change, that affects only the drawing of the red box, not the actual navigation :( This problem is purely a navigation problem.
the problem appears to be that the reported position of the users input ends up being negative numbers. Oddly, it is always the same pair of numbers (in this case it is -205, -504). Clicking the keymap again may result in the right value and the map will reappear. But it may not :( The actual navigation calculations appear correct based on the invalid input.
if you move the mouse over the main map image after the page has loaded, and then click the keymap, it will work every time. There must be some variable(s) that is not initialized until the mouse actually moves over the map image. Perhaps related to the javascript optimization of the main map image ...
fixed in beta 1 release version.
verified in using beta 2 2004-06-20
Verified on Fedora Core 1 Chameleon 20040625.
Forgot to close this bug.
