Infeasible
Status Update
Comments
cb...@google.com <cb...@google.com> #2
This is a browser bug related to user selectable zoom level.
br...@gmail.com <br...@gmail.com> #3
This appears to be the same issue I'm experiencing.
ra...@gmail.com <ra...@gmail.com> #5
I am experiencing the same issue. white lines are appearing in IE browser.
does any one know how to get rid of this?
does any one know how to get rid of this?
[Deleted User] <[Deleted User]> #6
[Comment deleted]
wi...@gmail.com <wi...@gmail.com> #7
I see white lines on my V3 map as well, but I only see it on the iPad
bi...@gmail.com <bi...@gmail.com> #8
Any updates so far? We are still dealing with this issue on a daily basis, whenever we print out the route for our fire trucks. Fascinating fact is - that issue is related only to our default browser which is Google Chrome. Printing works in Opera and Firefox. :(
ep...@gmail.com <ep...@gmail.com> #9
same here
ja...@gmail.com <ja...@gmail.com> #10
I have this same/similar issue with my custom google map.
In Firefox, Safari and Mobile Safari the map show up flawlessly.
In Chrome (for Mac) the position of the tiles are off by 2 pixels. I have made the background green to show the issue more prominently. The top and left styles are calculated incorrectly.
This is not an issue with browser zoom.
In Firefox, Safari and Mobile Safari the map show up flawlessly.
In Chrome (for Mac) the position of the tiles are off by 2 pixels. I have made the background green to show the issue more prominently. The top and left styles are calculated incorrectly.
This is not an issue with browser zoom.
ja...@gmail.com <ja...@gmail.com> #11
[Comment deleted]
gi...@gmail.com <gi...@gmail.com> #12
Having the same issue here with Chrome, a strange line of 1 white px keeps popping up!
me...@gmail.com <me...@gmail.com> #13
Same 1px crossing lines in chrome. safari and ie ok
bc...@google.com <bc...@google.com> #14
The bug you're seeing now in Chrome is different than what was originally posted here. If you'd like to get updates on progress, you want to look at Issue 6594 (or the underlying bug, which is actually in Chrome, which is being tracked here: https://code.google.com/p/chromium/issues/detail?id=362889 )
Description
The map where the bug is occurring: