IssueTracker

Can you check your browser zoom? This is often an issue when the zoom puts the tiles at non-integer pixel coordinates. You can reset the zoom by hitting ctrl-0.

If it's still a problem, can you provide a link to a page that demonstrates the issue? I see no problem when running the v3 samples, for instance.

It's definitely not a zoom issue. I'm sorry I should've provided that info.

My site at http://individual8.com/contact demonstrates the problem I'm seeing.

I'm seeing the same problem, and it definitely seems to be related to Chrome 34, both in Win7 and in OSX 10.9.2. No problem in FF or IE.

An example: http://jgromit.com/matrix/maps/gmaps.html?lat=45.9283&long=6.91227&type=hybrid&zoom=13&markertip=Photo%20location

I just posted a bug report at another thread before finding this thread: https://code.google.com/p/gmaps-api-issues/issues/detail?id=4120



In Firefox, Safari and Mobile Safari the map shows up fine.

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.


 

You can see the issue here: http://nobleespresso.com/#find

I have confirmed that this is a bug in Chrome.

I filed a bug here: https://code.google.com/p/chromium/issues/detail?id=362889

Hello I am still learning Code but will try to see if i can fix this as soon as possible :)

I'm getting this in Chrome 34.0.1847.116 m on http://discoverchina.info/my_china_trips/ (also screenshot at http://discoverchina.info/wp-content/uploads/2014/04/MP_screenshot.jpg). Not present in Firefox or IE. Zoom makes no difference.

I get a horizontal line on every map I generate at http://jacobsm.com/iptest.htm with the latest Chrome browser. Yet it works fine with IE11. My OS is Windows 8.1 64-bit Pro. The source to the page there is less that one sheet of A4 paper - I like to keep things as simple as possible! Any ideas? After all, it is Google maps on Google Chrome browser!

It'll be fixed in the next Stable release.

As stated in the Chrome bug here:
https://code.google.com/p/chromium/issues/detail?id=362889

So the only way to overcome these are... (Please anyone, who can confirm)

1-Recomend every client using current Chrome to wait for updates
2-Refer to v3.14 in the HTML that loads the Google Maps API

Am I correct or there's some other alternative to this?

Refer to v3.14 doesn't work for me.

I use Chrome 34.0.1847.116 in Mac OS X 10.8

Yes, it's unlikely this is fixable with 3.14, as it was really a Chrome issue.

The fix is in Chrome 35, which is currently scheduled for release in mid-May (you can switch to the beta channel to get the fix now or verify it in a Canary build - http://www.chromium.org/getting-involved/dev-channel).

Beyond that, there's not a whole lot to do to work around the bug since it's in the browser's renderer. There may be a way to tweak your map's sizing to not hit it, but that's going to be difficult in any page where the map size depends on the page size and layout.

[Comment deleted]

But I think that starting from v3.15 there are some inline styles applied to the tiles img element that involve the bug. I mean -webkit-transform:translateZ(0). That CSS transform is not applied on the tiles before v3.15 and thus it is possibe that the bug in Chrome is not expressed using the v3.14 API .

One correct URL to reference v3.14 API is

http://maps.google.com/maps/api/js?v=3.14&sensor=false

Here is a bin using v3.16
http://jsbin.com/wawezina/1

Here is a bin using v3.14
http://jsbin.com/wawezina/7

If you inspect this sentence in the console:

$("#map img")

, you can quickly check the transform that is applied inline to the tiles img

Having same issues on 34.0.1847.137 OS X 10.8.5
No help on switching API versions

Has anybody figured out how to overcome this issue?. I.e by wrapping the map div container with another div with a specific CSS rule or anything similar?

Still an issue in Chrome (34). Works fine in Canary.

definitely still an issue in v3.14.  hopefully this gets addressed soon

Hi. I applied to workaround of changing to v=3.14 and it worked fine just a few days ago. But from today when I checked again, the bug reappears even with the v=3.14 reference?

Could someone help confirm that something has changed for linking to 3.14. Thanks

With the latest release, v3.14 is no longer available.

https://developers.google.com/maps/documentation/javascript/basics#Versioning

I you request it you get v3.15

Chrome bug was fixed.

Same issues with current version of the maps

I am also facing same issue, I have checked all latest version and nothing works to me.

It is still not fixed in chrome. because I am getting white lines in my google map api as well. :(
it especially shows on polygon shapes like in my picture. in firefox there is no issue.

In google chrome canary the white lines (bug) is fixed :)

Still facing this issue, chrome version: 60.0.3112.113 (Official Build) (64-bit). Seems to be working fine on mozilla but not on chrome. any idea?

Any updates on this?

Any new updates or changes to this issue? Still occurring in Chrome but not other browsers.

This Chrome bug is still occuring. How is it possible that a huge and ugly bug like this is not fixed for years? Checking in: Edge. No problem. In Firefox: No problem. Even in Internet Explorer. No problem. In Chrome: still problem. Why is this not fixed and is there a workaround? How come this is not the highest priority?

Ok, I did the following and it actually helped a lot.

It is not the solution, rather it is hiding the problem, making it 50 % less noticeable.

It is by no means a real fix, just takes away half the pain, the lines are still there.

In your maps css:

#map_container > div {
background-color: rgba(128, 128, 128, 0.5) !important;
}

Where #map_container is the ID of the div element that contains your map.

It surely is a bug in webkit browsers not only Chrome.
I managed to fix this by adding this css:

    .gm-style div {
        -webkit-transform: scale(1.002);
    }

We are closing this old issue. Please star this similar issue instead https://issuetracker.google.com/153698495.