Develop Reference

google maps api versions issue

I have a problem regarding use of Google maps api.
When I use api source as
https://maps.googleapis.com/maps/api/js?v=3.9&sensor=true&libraries=places&callback=LoadMap';
then in my application pinch to zoom is not working. or in fact sliding of map is not working properly(it slides to one direction and sometimes doesn't even slide. many issues).
but when I use api source as
https://maps.googleapis.com/maps/api/js?key=XXX&sensor=true&libraries=places&callback=initialize";
then pinch to zoom is working and even sliding is working properly. But if I replace this with above 'api source' then info window that I created for above api is not opening.
Any Suggestion ? What to do. Is there any other api source I should use ?

Yes, 3.9 is older version and has pinch zoom broken on safari.
Try upgrading to a later version, or simply use the latest version like you have put on the non-versioned url

Highcharts zoom issue after upgrading to jQuery 1.8

I use Highcharts 2.2.5 to draw a number of area and bar charts.
I Just upgraded my app to jQuery 1.8 and started testing all my charts.
All appear ok, but when I zoom an area chart, I get tons (literally hundreds) of JavaScript errors saying "Error: Problem parsing d=0.99030204037363" (numbers change, sometimes d=1) and on the screen all I see are a bunch of dots where the chart was.
Resetting the zoom doesn't work either (yielding more errors, and no result). The only recourse at that point is to reload the page.
I tried looking online for any clashes between HC 2.2.5 and jQuery 1.8 but couldn't find anything. Switching back to jQuery 1.7.2 solves the problem, but still, one must look ahead...
Any assistance is appreciated,
Guy

After reporting the bug on github, per #MrObrian's suggestion, I got this reply:
It is already fixed for the next release - see
http://jsfiddle.net/highcharts/GJ4wR/. We're running the final tests
on that code now, hope to have it out by next week.
So all I have to do is wait 1 week :)

HTML5 Canvas drawImage issue in Windows 7 but only in Firefox

I'm having a problem with a program I'm developing (you can see it at www.energematrice6.com/gview2)
The galaxy viewer draws stars on 6 different layers. The back layers work fine (using a simple stroke command). The top 3 layers use the drawImage() functionality to take a saved image and draw it to the canvas (using the functions starGradDraw and starGradDraw2).
These images were created by another function when the program first executed and saved to an object variable (basically just a buffer).
Everything works correctly on my home computer, my laptop, my wife's computer, and just about every other machine I've tested this on (or had friends test it on).
When I tried to open it in Firefox 10.0.2 on my work computer (same version I use at home), the first three layers of stars are blank. The only other difference I can think of is that none of my home computers use a 64 bit operating system or specifically Windows 7.
Everything else still seems to work fine in the program, and firebug is not popping any errors. It's just not drawing the images (or halting the program). I'm really not sure what to try next.
Any ideas?
(I can paste some code if you like, but the program is over a thousand lines long and I'm not sure where the problem could be coming in or how it could error only on this machine.)

After rather a massive amount of research and bug-hunting, I've discovered that this problem is a bug in Firefox itself.
Apparently in the current version, with 2-D graphics hardware acceleration enabled, Firefox does not save radial gradients correctly when they are drawn directly to a buffer canvas (off-screen only).
Turning off hardware acceleration allows the browser to correctly process the commands.
A bug report has been filed and, hopefully, the issue will be fixed.

Chrome and SVG (Raphael), trouble with drawing "off-screen"

I'm working on a prototype system which will act as a proof of concept that an existing system can be made a lot more interactive.
It basically emulates our main software package but over the internet using JSONP requests to update a load of images and Raphael vectors to make it look like everything's running.
I'm having trouble on Chrome however with Raphael not drawing vectors "off-screen". What I mean by "off-screen" is that the main app runs through an iframe as it relies on cross-domain long poll comet through AJAX to get communicate back and forth. Below is an image demonstrating what I mean.
Here I've scrolled a long a little bit in the iframe to look at the bits "offscreen" and you can hopefully see that the grey arrows aren't rendered. I've used Chrome's developer tools to highlight over the SVN tag, showing that it's only given 450px by 810px to the SVG tag, which is the same size allocated for the iframe.
It's worth pointing out that it renders fine in Firefox. Any ideas?

I've had a similar problem and found a bug report for the WebKit project that seemed related:
https://bugs.webkit.org/show_bug.cgi?id=64823
According to the comments, it's a bug in the rendering engine and there's no workaround aside from losing the iframe or resorting to other means of scrolling the SVG viewport (like moving all the elements within the SVG element).
On the upside, version 16.0.912.21 has been released to the beta channel today and it seems that the bug has been fixed. I've also checked the latest chromium build (17.something) and the bug hasn't resurfaced. I'm guessing the fix should find its way into the stable channel in a couple of weeks.

Weird black spots on custom Google Map with IE

I'm getting some weird black spots with a custom map page (via the Google Maps API v2.x) I have created. (Click SERVICIOS and then the icon farthest south to generate image shown below.) The issue seems to only appear when using Internet Explorer. I'm wondering if this is a common problem and if there is a common fix?
Any ideas?
Thanks.
UPDATE
In this picture the browser is IE 8.0.6001.18702
Its hard for me to get specific details about the computer because my client took this screenshot, I have been unable to reproduce these black spots.
removed dead ImageShack link

This is completely related to the zooming feature in IE8. Ask your client to set his zoom level back to 100% and the black spots magically disappear. This is probably why not everyone can reproduce this problem, because it's a local browser setting. But even now (months later), when I follow your link -- or if I simply go to maps.google.com, do a search, and get the Marker/InfoWindow -- if I have the zoom level set to > 100%, I see those black shadow pieces where Google's javascript is trying to piece together the drop-shadow. So QED: Microsoft STILL has a bug in their scaling algorithm for transparent PNGs in IE8.
Weird black spots on custom Google Map with IE http://img340.imageshack.us/img340/751/googleblackholes.jpg

This black (png?) bug might be related to this issue:
IE 8 Black bug
What version of IE are you running? (Note that only some part of the drop shadow seems to be affected.)

I failed to reproduce this error (IE6,7,8,FF,Chrome), but I can offer you to try GMaps Utility Library. It allows to create custom info windows using css (live example that use ExtInfoWindow library extension). This library adds you an opportunity to create info windows without transparency which I think is a current problem.
I've tryed to look what google map API doing with info window at IE8 and found that it add CSS filter:
filter: progid:DXImageTransform.Microsoft.AlphaImageLoader(sizingMethod=scale,src="http://maps.gstatic.com/intl/ru_ALL/mapfiles/transparent.png");
Wich reproduce shadow under the info window based on transparent png image, maybe at your client computer this opportunity (filter) disabled, so I think the best solution is to use library i suggested.
Also you can try ie7-js library that has IE-PNG fix transparent functionality.

I had this blackspot too. It is generated by the <li>.
Remove the <li> and </li> around the affected area and it will disappear.