Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

11
  • @Myles jsfiddle is no longer working. Any ideas why? Commented Apr 16, 2015 at 1:02
  • 1
    @jmq yeah, it was pointing at an unpegged version of the library and the latest code works slightly differently. See this one for a working example jsfiddle.net/h11bxywo . Commented Apr 16, 2015 at 1:06
  • @Myles Thanks for the update. Looks like the jsfiddle shares the issue that I was having where the independent ui-gmap-window instance overlaps with the ui-gmap-markers instances. To fix that, I'm using the pixelOffset from the Google docs like so: pixelOffset: new window.google.maps.Size(0, -35) and then the info window appears above the marker as users would expect. Commented Apr 16, 2015 at 1:30
  • Mind you, my last comment should've used the $window Angular service rather than just window. Commented Apr 16, 2015 at 1:43
  • Hi, iit seems that coords="MapOptions.markers.selected.coords"' in your map-window` should be `MapOptions.markers.selected' without the coords. Because it is an object with lat and long. Commented Sep 22, 2015 at 4:31