Bump API version to support visualRefresh #347
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
+1 this. As a bump from 3.9 to 3.12 seems drastic I was wondering if you have noticed any regression issues? |
|
Not so far, but my use of the API is not extensive. |
|
Not seen any difference either on my current app, will test a bire more before accepting |
|
I've been on this for a little over a week and I'm not seeing anything out of the ordinary. |
apneadiving
added a commit
that referenced
this pull request
Jul 4, 2013
Bump API version to support visualRefresh
|
ok go! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Google has enabled opt in for their visual refresh by adding
google.maps.visualRefresh=true, but this option does not work on version 3.9 of the API which is currently being used.