Ios11 Causing Cors Issues in All Mobile Browsers

Apple iOS browsers randomly won't render HTML objects loaded dynamically

We couldn't find the exact source of this issue after a lot of investigation and are fairly sure this is a webkit bug. However there is an acceptable workaround, which is to replace the object tag with an iframe tag, and it looks to be working exactly the same way (replace .data with .src) with a bonus it doesn't exhibit the chrome bug where onload events are fired twice, so Chrome runs our app faster now.

How to fix iOS 12 Safari Cors preflight error?

It's a bug in iOSv12, but it's already fixed in iOSv12.1 beta (16B5059d), assuming the current beta code makes it into production.

The problem is that iOSv12 WebKit preflight OPTIONS calls don't leave the device. I've run WireShark and the iOSv12 simulator to confirm this.

iOS 11 Bluetooth URL Scheme

It looks like there's no solution at this time(9/19/2017) for this issue on iOS 11.

The codes below using UIApplicationOpenSettingsURLString to open the Settings.app works on iOS 11. Maybe it's a workaround at this time for you.

When you open the URL built from this string, the system launches the Settings app and displays the app’s custom settings, if it has any.

[[UIApplication sharedApplication] openURL:[NSURL URLWithString:UIApplicationOpenSettingsURLString]];

The code snippet in C#：

UIApplication.SharedApplication.OpenUrl(new NSUrl(UIApplication.OpenSettingsUrlString));

References:

• Anyone have anything on URL Schemes in iOS 11 developer Beta?

• How to open Location Services from iOS application for iOS 11 beta?

• Using App-Prefs:root=

z-index works on all modern browsers except Safari 7

You could solve this in Safari 7 by setting the z-index to what it normally is, then giving the style block the additional rule of pointer-events:none which would still allow the underlying text/elements to be selected as normal.

Provided there are no click elements on that circle or dragon, everything would behave exactly like you're expecting it to.

Of course, this would blow away support for browsers that don't have a full implementation of CSS 3, but it's the world we live in these days. You could always fall back to the negative z-index implementation for that scenario.

Edit: Without going into too much detail on your CSS, the likely culprit of your second failed scenario (the z-index on the header not appearing above those elements with a z-index) is likely due to the header not being given a positioning value other than static. You could probably fix this by giving it some stacking context by setting the CSS rule position:relative; on the element and then giving it a z-index greater than the stylistic elements.
e.g. .dragon{z-index:1;position:absolute;} .circle{z-index:1;position:absolute;} .header{z-index:2;position:relative;}

---

Related Topics