You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem? Please provide a link to a
demonstration page if at all possible, or attach code.
1. Load this example http://savedbythegoog.appspot.com/?id=3732ee0660d07cd0d801a9867945bf356eff4171
2. Notice how the zoom level on first draw is not the same one configured via the options.
3. Hit the redraw button, which forces a redraw with the _same_ zoomLevel. Observe
how the map visualization now uses the correct zoom level.
What component is this issue related to (PieChart, LineChart, DataTable,
Query, etc)?
Map visualization
Are you using the test environment (version 1.1)?
(If you are not sure, answer NO)
NO
What operating system and browser are you using?
Chrome / Linux, but it doesn't really matter for this specific bug.
*********************************************************
For developers viewing this issue: please click the 'star' icon to be
notified of future changes, and to let us know how many of you are
interested in seeing it resolved.
*********************************************************
Original issue reported on code.google.com by battlehorse on 2011-11-30 10:04:34
The text was updated successfully, but these errors were encountered:
Possibly related discussion on StackOverflow:
http://stackoverflow.com/questions/27605081/zoomlevel-parameter-for-google-visualization-not-working
fiddle demonstrating issue:
http://jsfiddle.net/1j59m61L/
Original issue reported on code.google.com by geocodezip on 2014-12-22 17:17:58
Thank you for your report. We have investigated this issue and have prepared a fix.
You should see the Map behaving as expected with the next release of Google Charts.
Original issue reported on code.google.com by grabks@google.com on 2014-12-23 16:30:25
Original issue reported on code.google.com by
battlehorse
on 2011-11-30 10:04:34The text was updated successfully, but these errors were encountered: