New Release

[pamela (Google employee)]

Hi developers-

We've just released an update to the API. See below for release notes.

Changed Issues:
- Fixed Issue 1363 : Bug: Map click events are not dispatched on the
iPhone

Other Noticeable Changes:
- Large zoom control is clickable in all browsers
- Infowindow "clears" the large zoom control, positioning itself fully
inside the map and controls
- Mobile copyright uses pretty images
- Tiles load from the center instead of the top left
- Users can no longer select the text of the map type buttons, or any
of the control images
- The main library is smaller by ~1.9 KB

These notes can also be found on the changelog:
http://code.google.com/p/gmaps-api-issues/wiki/JavascriptMapsAPIv3Changelog

Please test and provide feedback. Thanks!

- pamela

[pi5701]

seems you cannot select text and images in infowindow, too.

breaks my map in some way, cause i use the infowindow to show
coordinates and altitude to easy copy/ paste them to our taxonomy
database at the natural history museum of innsbruck/ tyrol.

link:
http://www.mario-baldauf.org/API_v3/index.html

[pamela (Google Employee)]

Hi pi5701-

Cool map. I'm able to copy the coordinates in the <input> boxes, but
not the text around them in the infowindow. Is that what you mean? If
so, please file a bug in the issue tracker. Thanks!

- pamela

[pi5701]

should work like on my old v2 map:
http://www.mario-baldauf.org/tlmf/map.html

selected content should be highlighted as normal

maybe add an option to make infowindow content selectable?

btw. can we expect an added doctype in next release?
hardly possible to make a more complex map crossbrowser compatible
without assigning a doctype

[pamela (Google Employee)]

I see, yes. Please file a feature request for making info window
content selectable:
http://code.google.com/p/gmaps-api-issues/issues/entry?template=Maps%20API%20v3%20-%20Feature%20Request

- pamela

[pi5701]

added feature request infowindow content selectable: true/ false:

http://code.google.com/p/gmaps-api-issues/issues/detail?id=1415&q=apitype%3AJavascript3%20type%3AEnhancement&sort=-stars&colspec=ID%20Type%20Status%20Introduced%20Fixed%20Summary%20Internal%20Stars

[Van Thieu]

V3 Maps API cannot coexist with the jquery API.

[Ben Appleton]

Why is that?

[S.Buescher]

Pamela,

Might I suggest that you add the iPod Touch when checking for
useragent in the example on this page:
http://code.google.com/apis/maps/documentation/v3/

That is, check for 'iPod' as well as 'iPhone'

Steve

On Jun 12, 10:35 am, "pamela (Google employee)" <pamela....@gmail.com>
wrote:

[pamela (Google Employee)]

Good idea, Steve. I'll pass that on.

- pamela

[pamela (Google employee)]

Hi developers-

We've just released an update to the API. See below for release notes:

Fixed Issues
* Issue 1415 : infowindow content: selectable true/ false
* Issue 1432 : Mouseout event doesn't trigger after set_icon is
called
* Issue 1365 : Map Type Controls render incorrectly with strict
doctype

Other Noticeable Changes:
* Developers no longer need to specify size for a MarkerImage, the
API will detect it when not provided. On a related note, the size,
anchor, and origin arguments for MarkerImage are all optional.
* Developers no longer need to call OverlayView.call(this) in an
OverlayView subclass's constructor.
* The OverlayView "changed" methods were removed from the interface.
This should not affect developer's code.
* The partialmatch option was removed from Geocoder Request objects.
If a developer continues to pass it, it will have no effect on the
query. (Note: upcoming geocoder changes make this option obsolete,
there should be a post about that next week).

[pi5701]

nice ones, thx

scrollwheelzoom, draggable markers, option to add custom tileURL,
polylines and doctype declaration are the things im waiting from now
on.
would be cool to see any of those added after holidays.

- pistol

[pamela (Google Employee)]

Be sure to star the relevant feature requests then :)

http://code.google.com/p/gmaps-api-issues/issues/list?can=2&q=apitype:Javascript3%20type:Enhancement&sort=-stars&colspec=ID%20Type%20Status%20Introduced%20Fixed%20Summary%20Internal%20Stars

[bratliff]

On Jul 13, 5:57 am, "pamela (Google employee)" <pamela....@gmail.com>
wrote:

> * Developers no longer need to call OverlayView.call(this) in an
> OverlayView subclass's constructor.
> * The OverlayView "changed" methods were removed from the interface.
> This should not affect developer's code.

The "zoom_changed" & "offset_changed" events are still firing,
sometimes repeatedly.

See:

www.polyarc.us/tile

Additional "bounds_changed" & "center_changed" events would be very
useful.

See:

http://code.google.com/p/gmaps-api-issues/issues/detail?id=1395

[pamela (Google Employee)]

Thanks, bratliff. I replicated that issue and reported internally.

[pi5701]

concerning infowindow content:selectable true/ false:

if i rightclick infowindow now 'google.maps.event.addListener
rightclick-function' is
fired instead of showing contextmenu
link:
http://www.mario-baldauf.org/tlmf/API_v3/index.html

leftclick map - rightclick infowindow - red-circle-memomarker is drawn
on map underneath infowindow

-pistol

[Ben Appleton]

Hi developers-

We've just released an update to the API. See below for release notes:

Fixed Issues

 * Issue 1393 : Allow draggable markers
 * Issue 1448 : Bug: API v3 needs a checkResize() function (or equivalent)
 * Issue 1404 : Error with cursor in Opera
 * Issue 1514 : MapType select arrow displayed incorrectly with HTML 4.01 strict

Other Noticeable Changes:
 * Pinching and dragging on the iPhone should be more robust.

Please test and provide feedback. Thanks!

- Ben