| Issue 3407: | Autocomplete's firing of place_changed event doesn't satisfy specificaion | |
| 12 people starred this issue and may be notified of changes. | Back to list |
As per the Google Maps V3 API spec found here http://goo.gl/YdWCC, the place_changed event should fire: 1) "when a PlaceResult is made available for a Place the user has selected." AND 2) "If the user enters the name of a Place that was not suggested by the control and presses the Enter key, a place_changed event will be fired that contains the user input in the name property, with no other properties defined." This is true on maps.google.com, however, specification #2 is not working in the API, as seen by Google's example here: http://goo.gl/hUufm.
Jun 20, 2011
(No comment was entered for this change.)
Status:
Confirmed
Aug 10, 2011
Same problem here
Aug 14, 2011
Yeah, I am running into problem here, too. I tried using onchange instead, but that is broken, too. (Refer to issue 3541 that I just filed.)
Sep 26, 2011
Having issues with this as well. If autocomplete fails to find a location I want to try to geocode the search text. For example, autocomplete will not encode cross streets but the geocoder will. If both autocomplete and geocoding fail I'd like to display an error message of some sort, but without being able to detect the onchange of the text field or have place_changed fire when they've submitted the form it's impossible to get the form's state.
Oct 28, 2011
Please fix!
Dec 15, 2011
(No comment was entered for this change.)
Status:
Fixed
Labels: Fixed-3.7 |
|
| ► Sign in to add a comment |
Labels: Internal-4671419