OpenCPU fail on mobil devices - r

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.

Related

Safari and Edge can't load sites (sometimes, very often!)

Please, I need help about a strange behaviour of our server.
The server (Microsoft Windows Server 2012, IIS 8.5, Plesk Onyx 17.8.11) hosts a lot of sites developed in different technologies (PHP, ASP.NET, HTML+JS).
These sites work well with Chrome and FireFox both on Windows and MacOS, but Safari on iOS 11 & 12 is unable to open the sites, so I get this error "safari can't open the page because the server where this page is located isn't responding".
Sometimes Safari open the site for a few minutes, then it don't work again.
I experience a similar in Microsoft Edge: it can't open the sites unless I run Fiddler, in this case it works well.
I'm getting crazy, because this behaviour seems to be unpredictable.
Thank you in advance.
There are many compatibility issues for safari (I can't speak for edge). If you inspect the CSS code of these particular sites that you are having trouble running, and with some research, you will likely be able to identify the lines of code that are causing the sites not to load on Safari.

TypeError: Unable to delete property

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

doc.meteor.com does not work well with Mac Safari 7.0.1?

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.

Internet Explorer 10 FCKEditor problems

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.

What's the most efficient and reliable method to test CSS design in multiple legacy browsers?

I'd be very interested to hear what professional developers think about this, particularly frontend developers.
How do you go about testing your designs in multiple browsers? Do you use virtual machines, each with a different version of Internet Explorer installed? What is your setup/workflow?
So, what's the most efficient and reliable way to test a design in several legacy web browsers?
Thank you.
I mostly use Spoon virtualization. They removed IE from the service aftyer Microsoft told them to however it's still a good service for testing other browsers/versions.
For IE I tend to use the Microsoft provided IE VMs.
If you need virtualization product then VirtualBox is pretty good and free.
I've also just discovered Browserling which does something similar to Spoon virtualization and has support for multiple IE versions.
Oracle's VirtualBox is free. I have the following VMs set-up:
Windows XP - IE6, Firefox 3
Windows XP - IE7, Firefox 4
Windows Vista - IE8
Really, I don't test older versions of Firefox, Chrome, or Safari. All three of those browsers are on quick update cycles now and the push their updates almost immediately. The chance that users are still using an older version of those is much less than those using Internet Explorer.
Even now, I don't really test in IE6 anymore (thank god), but I know this is different depending on the audience of your website.
Really, if you can get away with it, do your basic testing in IE 7, 8, 9 and the latest versions of Firefox, Chrome, and Safari. Don't go completely out of your way to fix layout issues in older IEs; If you can get the information you want from the site, then the site is functioning. If someone complains about the site not looking exactly right, recommend they upgrade or switch browsers. "I can't upgrade from IE6 because my company uses it" is not really a valid excuse anymore with Chrome and Firefox being as light weight as they are, unless their computer admins have things completely locked down.
IE Tester allows to see web from ie5 till ie9.
http://www.my-debugbar.com/wiki/IETester/HomePage
It depends how legacy you wonna go but there is also Adobe browser lab.

Resources