I got a clue regarding the scroll-bar issue: If you reduce the size of your browser on the screen and open the released version, you see of course only half of our welcome screen. If you extend your browser window then to full screen, the welcome page adapts perfectly. However, when you open a map, the scroll-bars are located where the previously reduced window ended. Maybe that helps to identify the problem in the code. The problem is mainly that there does not seem to be any regularity in producing misplaced scroll-bars.
I was able to repeat the observation both in Chrome and Firefox.
I got a clue regarding the scroll-bar issue: If you reduce the size of your browser on the screen and open the released version, you see of course only half of our welcome screen. If you extend your browser window then to full screen, the welcome page adapts perfectly. However, when you open a map, the scroll-bars are located where the previously reduced window ended. Maybe that helps to identify the problem in the code. The problem is mainly that there does not seem to be any regularity in producing misplaced scroll-bars.
I was able to repeat the observation both in Chrome and Firefox.