Fixed
Status Update
Comments
fr...@gmail.com <fr...@gmail.com> #2
I second the motion: please add an option to disable continuous zoom.
In my case we have just migrated from v2 to v3 and all of our icons have begun to experience a momentary increase/decrease in size during each scroll action (didn't happen in v2 becase we didn't have continuous zoom switched on).
This is now causing confusion amongst our user base, so it would be great to be able to prevent it from happening by switching off continuous zoom.
In my case we have just migrated from v2 to v3 and all of our icons have begun to experience a momentary increase/decrease in size during each scroll action (didn't happen in v2 becase we didn't have continuous zoom switched on).
This is now causing confusion amongst our user base, so it would be great to be able to prevent it from happening by switching off continuous zoom.
lu...@google.com <lu...@google.com> #3
Continuous zoom appears to be causing a regression bug within FireFox 4 when using custom overlays.
As a premier customer, this is a big deal. Having the ability to disable this feature would allow us to mitigate the effect as a solution is determined.
As a premier customer, this is a big deal. Having the ability to disable this feature would allow us to mitigate the effect as a solution is determined.
fr...@gmail.com <fr...@gmail.com> #4
William,
What is the regression? Is it limited to FF4 only? Could you post a demo link please?
What is the regression? Is it limited to FF4 only? Could you post a demo link please?
cb...@google.com <cb...@google.com> #5
Continuous zoom is crap. Try zooming with the slider from z=18 to z=0 and Firefox hangs for 30 seconds. Give us a way disable this please!! Even better disable by default cause it's crap, then let people enable it if they want it.
If it was such a great feature why doesn'tmaps.google.com use it???
If it was such a great feature why doesn't
cb...@google.com <cb...@google.com>
sh...@gmail.com <sh...@gmail.com> #6
I say if the zoom level changes +/- more than 1 then don't use the feature. If you're just stepping incremently between zooms, I guess it works okay. Or Animate the transition over a longer period of time, but then that'll take too long.
you really notice this problem when using the fitBounds() function...
you really notice this problem when using the fitBounds() function...
Description
<!DOCTYPE html>
<html>
<head>
<title>
Google Maps JavaScript API v3 Example: Asynchronous Map Simple
</title>
<meta name="viewport" content="initial-scale=1.0, user-scalable=no">
<meta charset="UTF-8">
<link href="
rel="stylesheet" type="text/css">
<script type="text/javascript">
function initialize() {
var myOptions = {
zoom: 8,
center: new google.maps.LatLng(-34.397, 150.644),
mapTypeId: google.maps.MapTypeId.ROADMAP
};
var map = new google.maps.Map(document.getElementById('map_canvas'),
myOptions);
}
function loadScript() {
var script = document.createElement('script');
script.type = 'text/javascript';
script.src = '
'callback=initialize';
document.body.appendChild(script);
}
window.onload = loadScript;
</script>
</head>
<body>
<div id="map_canvas"></div>
</body>
</html>
And here is the above, tweaked as minimally as possible to conform to XHTML. The map itself paints very nicely, but the controls at the upper left are duplicated, two sets of images, separated vertically by approximately 50 pixels. Same effect under both IE 9.0 and Safari 5.1.2:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "
<html xmlns="
<head>
<title>
Google Maps JavaScript API v3 Example: Asynchronous Map Simple
</title>
<meta name="viewport" content="initial-scale=1.0, user-scalable=no"/>
<meta charset="UTF-8"/>
<link href="
rel="stylesheet" type="text/css"/>
<script type="text/javascript">
function initialize() {
var myOptions = {
zoom: 8,
center: new google.maps.LatLng(-34.397, 150.644),
mapTypeId: google.maps.MapTypeId.ROADMAP
};
var map = new google.maps.Map(document.getElementById('map_canvas'),
myOptions);
}
function loadScript() {
var script = document.createElement('script');
script.type = 'text/javascript';
script.src = '
'callback=initialize';
document.body.appendChild(script);
}
window.onload = loadScript;
</script>
</head>
<body>
<div id="map_canvas"></div>
</body>
</html>
What is causing the duplication of the controls at the upper left of the screen?
My interest in XHTML is not academic. I am attempting to submit a product to the Apple iBookstore, which requires EPUB compliance, which requiress XHTML compliance. My product utilizes Google Maps, which operate perfectly under HTML but fail under XHTML. A forum suggestion to use the asynchronous loader for XHTML operation was helpful, but resulted in the double vision of the controls. Thanks.