Jul 4, 2016 Project Member #125 [email protected] Issue 10052 has been merged into this issue. Here is our code snippet for further review. Anyway, hopefully someone can use this solution. At line 0, char 0? have a peek here
Google_map.png 187 KB View Download google_map_v3.23_script_error.JPG 99 KB View Download google_map_v3.24_script_error.JPG 100 KB View Download Jun 19, 2016 Project Member #114 [email protected] #113 We're You need to run mfcie.exe in the release folder of the mfcie project. Feb 16, 2016 #43 [email protected] Hello, i created this jsfiddle as you ask: https://jsfiddle.net/4qrymm9g/1/ But you can't reproduce the problem in this manner, it works. Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name read this post here
none of the above work unfortunately. Feasibility of using corn seed as a sandbox How to limit a xorg installation to a single video driver? I switched the map from hybrid to satellite in the initialization file and the js.onion error went away when compiling. Please add the meta tag, which tell your webview to use Edge, which is a supported browser, and that should do the trick.
The code uses a Visual Studio webbrowser object which might be part of the problem. I ran your test and window.JSON is NULL. Like this: http://maps.google.com/maps/api/js?sensor=true&v=3.22 share|improve this answer answered Dec 29 '15 at 18:38 Giovanny Farto M. 655612 1 worked for me too.. I also reverted back to v 3.22.
Not the answer you're looking for? The error message no longer appeared. But again, it is impossible to guess anything out of your (working) code. http://stackoverflow.com/questions/19156453/google-api-v3-getting-js-error-in-google-main-js I still get the error.
Perhaps you could provide more details of your browser and the script to enable Google to resolve the issue. The only work around I have is fixing the google api version to &v=3.22. share|improve this answer answered May 27 at 15:39 NOSUKE 291 Repost .. This happens despite the fact that I call google.maps.controlStyle = 'azteca'; before I define a map object...
This thread mainly deals with people using webviews who got IE7, if you're in a similar situation, can you make it use Edge, or a modern IE version? http://fileupster.com/google-maps/addlistener-google-maps.html How exactly does mining software work? thanks mate! –Christopher Townsend Jan 14 at 17:05 2 Not recommended. The alternative is supporting IE7 (and 6?
I found only the IE7 emulation to fail. mouseover.png 62.5 KB View Download Feb 15, 2016 Project Member #42 [email protected] Yes, version 3.23 has become stable. What is 'onion.js' trying to do? Check This Out Looking at various documents it seems it defaults to IE 7 but can be encouraged to use later versions with registry entries.
How do we get Google to solve this problem? It is an IE11 that's is in IE7 mode, so it is an IE11 that has the JS of IE7. Unfortunately this is where our supports stops, as you would understand, as this is an issue with IE not the JS that we ship.
Browsers supported –geocodezip Nov 28 '15 at 18:38 1 An update was recently released to the API: (Release Notes). I think it's fair to see that there comes a point where browser support simply has to be ceased. more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed Also, I can't use it with my app as it uses a modern feature.
Appease Your Google Overlords: Draw the "G" Logo How can I Avoid Being Frightened by the Horror Story I am Writing? Feb 29, 2016 #62 [email protected] #58 works for me. Please! this contact form Why must the speed of light be the universal speed limit for all the fundamental forces of nature?
Jun 3, 2016 #93 [email protected] Hi, Back with more questions about the IEFrame.dll version and the script error at URL http://maps.googleapis.com/maps-api-v3/api/js/23/10/onion.js. If this turns out to be the problem, I suggest to close this bug, as IE7 is really not a support version anymore.