Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account

Maps appearing as incorrect sizes

This is actually a problem I have experienced for quite a while now with the maps but haven't reported due to it being a bit of a minor bug. With certain sizes of maps, the amount of squares shown are incorrect. In the below example the map is set to 20x20 squares which are filled out by the planks. 2 extra columns of squares are visible in the right side though (which don't seem to add to the amount of scrolling I can do towards the right, ie, I can't scroll further to the right than shown). Changing the map size to 19x19 gives this result: Which looks normal. Another example here with rows at the bottom: Notice the white background at the bottom. It only appears when there is still space between the top line of the browser and the map (notice the little gap between the browser bar and the picture). The above map was 40x11 squares (grid turned on, it's simply transparent). Here the white background is gone again after scrolling a tiny bit down so that a bit of the browser bar covers the image. I've asked my players to check if they see the same thing and most of them do, one of them don't. It only seems to appear in Google Chrome and all the people who said they saw it has a screen resolution of 1920x1080. It seems to appear semi-randomly otherwise, one of my players don't see it, I see it constantly though. Both me and all my players are using either Windows 7 or 8.1. OS: Windows 8.1. Chrome version: 35.0.1916.114
I believe this is a known issue where the canvas is displayed at an incorrect size when certain zoom levels are used. The map is still the right size, but it gets displayed larger. I'll add this to the error tracker thread. Thanks for reporting it.