Google Maps api v3 tools: visual distortions?

Asked 19/12, 2012 at 22:35 Answered 18/2, 2015 at 14:36

Solved css google-maps-api-3 css-position appearance

I just noticed that the gMap view tools are displaying…rather unusually. Their regions still seem to be properly defined—I can interact with them just fine, it's just their appearance that looks messed up.

I haven't applied any CSS to any of the map pieces, and the only css I've applied to the map container is width:100%; height:100%; z-index:0; (which I normally do).

I do have other elements on the page which have position:absolute; and position:fixed; and some high z-indexs (500 & 1000). Is it possible they are causing the visual distortion of the Map's tools?

I see the same weird visual distortion in the latest versions of Chrome, Chrome Canary, Ffx, Safari, and Opera (on Mac OSX).

I checked dev tools / firebug, and no unexpected CSS is being applied to the map's container or directly to its tools.

Google Maps Api v3: Map interface tools

Here is the exact HTML (I stripped out the other elements and css and the weirdness still happens):

<html style="width:100%;height:100%;">
    <head>
        <link rel="stylesheet" href="shared/bootstrap/css/foundation.min.css">
        <link rel="stylesheet" href="shared/bootstrap/css/v2.2.2.min.css">
        <script
            type="text/javascript"
            src="http://maps.googleapis.com/maps/api/js?key=...">
        </script>
        <script type="text/javascript">
            function ginit() {
                var vancouver = new google.maps.LatLng(49.285415,-123.114982);
                var mapOptions = {
                    center: vancouver,
                    zoom: 15,
                    mapTypeId: google.maps.MapTypeId.ROADMAP
                };
                var map = new google.maps.Map(
                    document.getElementById("map"),
                    mapOptions
                );
                var infowindow = new google.maps.InfoWindow(),
                    marker;
            }//ginit()
        </script>
    </head>
    <body onload="ginit();" style="width:100%;height:100%;">
        <div id="map" style="width:100%;height:100%;"></div>
    </body>
</html>

EDIT: It appears the issue is coming from the combination of Foundation and Bootstrap: removing either one fixes the issue. Also it doesn't matter that no elements on the page reference classes from the libs, it causes the distortion all the same.

I tried to put this up in a fiddle, but I couldn't get jsfiddle.net to load.

Order answered 19/12, 2012 at 22:35 Comment(8)

Just this new project? All projects? On one computer? All computers? Can we see a demo? Not much to do here otherwise. – Clarendon 19/12, 2012 at 22:40

I'm only working on one project at the moment. And I've tested it on 2 computers: OSX 10.6 & 10.8. I'm working on a dumbed down fiddle (there's a lot of framework stuff happening that I have to strip out), but I'm having trouble accessing jsfiddle.net. – Order 19/12, 2012 at 22:43

Yeah, for some reason jsFiddle is very slow right now. You're doing the right thing by making a demo, but this is exactly why questions should not rely solely on jsFiddle to show their code. – Clarendon 19/12, 2012 at 22:48

Oh my there's definitely too much code to post in my question ;) – Order 19/12, 2012 at 22:51

You are expected to post a concise question containing the bare minimum code required to reproduce the problem... it's the only way these questions can remain useful for others in the future. If it's too much code to post, then it's the type of question that probably doesn't belong here. i.e.- "find my problem buried somewhere on this site", etc. – Clarendon 19/12, 2012 at 22:53

My question is basically if anyone has encountered something like this before, or how could elements from outside the map's container affect the display of its tools (to which the API applies inline css). – Order 19/12, 2012 at 23:1

If that's your question, then it does not follow the format for SO. We're here to help you find programming solutions for specific pieces of code, not general troubleshooting sessions or discussion. – Clarendon 19/12, 2012 at 23:4

to sort this out, set .gmnoprint img {max-width:none}. [source][1]. [1]: #9904879 – Hibbert 27/5, 2014 at 16:21

For the future users who face same problem, here is the fix.

#map img{max-width: inherit;}

Like other answers said it is problem with max-width.

Earpiece answered 13/1, 2013 at 18:50 Comment(1)

#map img {max-width: inherit !important; max-height: inherit !important} – South 26/3, 2015 at 2:54

Bootstrap and Foundation set { img max-width:100% } for Google Maps canvases. This causes the Maps controls to appear distored. Alter the css to be max-width:none;. [source]

Caveat: Apparently img { max-width: 100% … } is integral for images auto-resizes for responsive layouts, so use with caution. [source]

Order answered 20/12, 2012 at 0:48 Comment(1)

Yes, #map-canvas img { max-width:none; } fixed this for me. – Outwash 19/12, 2014 at 2:4

Foundation 5 no only breaks gmap, it also breaks MapQuest. Luckily both Goomap & Quest have class to allow us to overload F5 behavious only for maps display.

.google-map {
  height: 400px;  // no default height
  color: #191970; // default color for both text and background is white !!!
}

.quest-map {
  height:400px; 
  color: #191970;
}

// Fix Foundation bug with MapQuest
.mqa-display {
  img {max-width: none;}
  label { width: auto; display: inline; }
}

// Fix Foundation bug with GoogleMap
.gm-style {
  img { max-width: none; }
  label { width: auto; display: inline; }
}

Interchange answered 18/2, 2015 at 14:36 Comment(0)

Recommended topics

Hot tags