Even when the most basic map loads the following error is shown:
TypeError: Unable to delete property.
This has to do with the zoom, as with any zooming, the error is shown again.
I have tried to reset the map to v 3.5
https://maps.googleapis.com/maps/api/js?v=3
and it worked for a few days, then the same error happened again.
Going back even further to v3 would not help anymore. What happened and how could this be fixed?
BTW: the problem does NOT occur with CHROME/FIREFOX BUT with SAFARI (5.1.1)
TL;DR: The support for Safari 5.1 has stopped. Solutions are upgrading the browser or use a different one.
The new version of Google Maps was announced here. AFAIK the newest stable version of Google Maps is shipped since 17.12.2014 (v3.18) and does not support any version of Safari < 6.
I've found this answer from a Google Staff here:
Apple has retired Safari 5.1 (and OS X 10.6 in general), last issuing
a (security-only) patch over a year ago. Likewise, the Maps API is no
longer supporting that browser (as discussed in the FAQ as well as a
few other places:
https://developers.google.com/maps/faq#browsersupport).
Browser migration is painful and sites often have no control over what
browsers their users visit with, but -- as browsers age -- a line must
be drawn somewhere. Safari 5 last got a major feature update nearly 3
years ago (in 5.1.4) and can no longer keep up with what's needed from
it.
Users really should not be on OS X 10.6 either (as its last security
update was at the same time as Safari 5's, in September 2013), but the
good news for those who won't or can't update is that the latest
versions of both Chrome and Firefox still support 10.6, and both of
those are well supported by the JS Maps API.
For me the changelog was a little confusing:
The current and previous version of Safari (Mac OS X)
This apparently does not cover discontinued versions of Mac OS X. Also Safari for Windows is not mentioned. Looking at the support timeline for Safari Windows is no longer supported anyways.
Changelog of the Google Maps API
Browser support of Google Maps Javascript API
Related
Has Google has unofficially decided to depreciate the Earth API without officially telling anyone?
Chrome on Mac rev 39 no longer works
Windows Chrome 64-bit user will have the same issue.
Chrome 64-bit supports only 64-bit NPAPI plugins
https://support.google.com/chrome/answer/6083313?hl=en
The advice given so far has been to have users revert to an older version of chrome.
For Windows users using Google Chrome 32-bit, the Earth API is only supported up to Chrome rev-35
https://developers.google.com/earth/documentation/index#installing_the_google_earth_plugin
I submitted a enterprise support ticket and have been told that Chrome support officially ended for Chrome rev 37 for both Windows and Mac
I can understand the Chrome team desire to retire NPAPI, but there has virtually no response or notification and depreciation from the geo end of things.
I've seen lots of notice on the depreciation of the "Flash Maps Api" and "Maps V2"
It took a few weeks, but the answer unfortunately is yes
http://googlegeodevelopers.blogspot.ca/2014/12/announcing-deprecation-of-google-earth.html
I have recently begun toying with OpenCPU and I must admit I am very impressed with it. Though, I have run into a strange problem.
When I try to access an application that I am currently working on, on my laptop, everything is fine. But when I do it on a mobile device, I get an error.
"Connection to OpenCPU failed: error"
Any thoughts on why the error is occurring?
I have uploaded an example to www.ttbjerring.com
Best,
Bjerring
Some debugging and google reveals that there are multiple problems with the CORS implementation in older versions of Safari. The main issue seems to be that the client can not read the Location header:
Cross Origin XMLHttpRequest can not expose "Location" header even if it is indicated in Access-Control-Expose-Headers
All of this has been fixed in more recent versions of Safari. Do note that Safari for windows is no longer supported by Apple. The latest Windows version (Safari 5) was released in June 2010, with a final patch release 5.1.7 in May 2012. So it has not been updated for over two years.
Now Safari Mobile is more problematic of course. I don't have an iphone/ipad myself, but it would be helpful to further narrow this down. Which version of Safari/IOS are you using? Did you get a chance to test this on a more recent versions of Safari Mobile? It would be nice to have a workaround, but it might not be easy.
I did push and deploy a small fix for another problem that Safari seemed to be having in some cases, but I doubt this will solve any of your problems.
I've been using Mac (Mavericks) Safari to lookup docs.meteor.com but of late, Safari was not able to read the site. The location bar keeps refreshing and no page appears.
I think the latest 0.7.0.1 may have broke it. Any one experiencing the same issue?
Apparently, there is a known problem as discussed in this thread at meteor-talk google group:
https://groups.google.com/forum/#!topic/meteor-talk/ZzQVdcdz33Y/discussion
It seems to work when dev tools is open and now work when it is closed.
Hello Stackoverflow community.
Since the release of Windows 8 and thus, Internet Explorer 10, FCKEditor refuses to function with IE10. With the latest patches, Firefox 17 and Chrome work just fine with it.
I know FCKEditor is old, so I was thinking of moving to CKeditor but it seems, its implementation for classic asp webpages doesnt work with IE10 as well.
Any suggestions, on how to fix the problem, or any other editors (with the functionality of the above two editors) would be appreciated(classic asp only).
CKEditor should work with IE10.
Maybe there are some problems with it at the moment (I tested it briefly some time ago), but given that it's a supported version (opposed to the status of FCKeditor), if you file bugs reporting the problems they should be fixed eventually.
I've been testing a website I design on my mac and also on windows. To be more specific mac osx snow leopard and windows 7.
Now I'm wondering if I will need to test further e.g. mac osx leopard, tiger ... windows xp, windows vista?
I've been wondering since I started all this browser testing stuff.
Kind regards
The only browser that's an issue IMO is IE as running multiple versions takes some setup and is not completely decoupled from the OS. The Developer Tools in IE 8/9/10 let you choose the rendering mode of earlier versions, but there are sometimes differences in the rendering between the simulated and "native" browser. Users of the other browsers (Firefox, Chrome, Opera, Safari) tend to upgrade quickly and in addition, even early versions of those browsers were fairly compliant (aside from CSS3 capabilities that were codified after they were released, but those usually degrade gracefully)
Great article in Smashing Magazine about setting up testing for IE using virtual machines.
Fonts are dependent on if the user's OS has them installed by default. Fonts have kerning (space between the characters), and if changed to a backup font with different kerning can affect the flow of your page.
Form elements (text inputs, radio buttons, dropdowns, etc.) are rendered by the browser but adhere to the OS standard settings.
In short, it's always good to get your hands on as many environments (OS/browser combinations) as possible to see what your site will look like. If you have a friend with a different set up, check it out, ask them to send you a screenshot or use one of the online services that provide this ability.