Style sheet rendering is significantly different between Safari and Windows. To see this, try creating a page that has an element with a z-index of -1.

1. Safari For Windows 10

Safari Windows is still at beta 3.03 so there are some huge differences for now 😉 If you are an Apple Developer Connection member (free) you can get some access to more. There is also public WebKit project (core used for both versions) that you can use to test with and see what the current build status is.

The windows version will function without issue, the Mac version will not allow you to select the elements. Trust me, I wasted about three hours trying to figure out by trial and error why a page would work in one system but not the other. The worst bit is that when Safari doesn't render something properly, it does so without any indication. You have to debug line for line, a dreadful experience. A call to java from javascript throws: java.net.MalformedURLException: no protocol: at java.net.URL.(Unknown Source) at java.net.URL.(Unknown Source) at java.net.URL.(Unknown Source) at sun.plugin.liveconnect.SecureInvocation.checkLiveConnectCaller(Unknown Source) at sun.plugin.liveconnect.SecureInvocation.access$000(Unknown Source) at sun.plugin.liveconnect.SecureInvocation$2.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.plugin.liveconnect.SecureInvocation.CallMethod(Unknown Source) on Safari windows but not safari mac. Just wanted to add this experience I came across for Safari.

Our devs are still going to look into this but not high priority for us since Windows Safari isn't much of our user base unlike Mac. Download hp deskjet 3051a driver. But I think it relates to either (or both) - actual browser low level implementation of Safari by Apple, and/or javascript differences. Our website recently implemented an HTML5 multiple file uploader. Single file uploads work fine on both versions of Safari.

Safari For Windows 10

But when uploading multiple files, it fails on Windows. We had two different upload clients & endpoints for the uploader (think A/B testing flow), and one of them provided more details that may or may not point at the cause of the problem. On one of the client & endpoints, the client would send details of the filenames & filesizes of files to upload (as JSON array object) to the server endpoint (as seen via web inspector). On Mac where it worked, filesizes were valid, on Windows, they were 0 bytes. I think the uploader is JQuery based or some other JS library. But I'm not the dev, so can't be sure.