You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: Totor [Submitted to the original trac issue database at 11.29am, Wednesday, 16th January 2013]
On firefox 12.0 (on eeepc, xandros linux) the left side of the website (menu) can not fit in the screen (this can be simulated by reducing the height of the window on larger screens). When using the scroll bar to go to the bottom of the page, the page/menu scrolls, but the map remains on the top of the page "floating".[[BR]]
Once completely scrolled down to see the partners link, a click in the zoom bar, to directly select a zoom level of the map, will go to a very low zoom level.[[BR]]
It looks like the displayed zoom bar is linked to the "floating" map, but the real clicking zone (or zoom level computation) scrolled down/up with the rest of the page.
FF18 under ubuntu still has the same problem.
IE8 and Chrome do not seem to have any problem.
The text was updated successfully, but these errors were encountered:
Reporter: Totor
[Submitted to the original trac issue database at 11.29am, Wednesday, 16th January 2013]
On firefox 12.0 (on eeepc, xandros linux) the left side of the website (menu) can not fit in the screen (this can be simulated by reducing the height of the window on larger screens). When using the scroll bar to go to the bottom of the page, the page/menu scrolls, but the map remains on the top of the page "floating".[[BR]]
Once completely scrolled down to see the partners link, a click in the zoom bar, to directly select a zoom level of the map, will go to a very low zoom level.[[BR]]
It looks like the displayed zoom bar is linked to the "floating" map, but the real clicking zone (or zoom level computation) scrolled down/up with the rest of the page.
FF18 under ubuntu still has the same problem.
IE8 and Chrome do not seem to have any problem.
The text was updated successfully, but these errors were encountered: