Iframe content not loading in Iphone after IOS15 upgrade - iphone

We have a custom application embedded in an iframe and the content inside the iframe is not loading only in Iphone after the ios is upgraded to ios15. The same application is working fine in IOS14. This issue is seen both safari and chrome browsers after IOS15 upgrade.
The same application works fine in Android Mobiles and Desktop mobiles. Are there any known issues with IOS15 with respect to Iframe? Any pointers to solve this issue will be greatly appreciated.
-- Satish.

My English is poor,I'll try to be as concise as possible.
Because IOS15 cannot use iframe to embed cross-domain web sites.
Some solutions:
Redeploy the custom application embedded in the iframe,ensure that the site in the iframe is in the same domain as the parent page.Avoid cross domain.
or,Configure proxy forwarding to the server where the parent site is deployed,For example, nginx configures proxy forwarding to the application embedded in an iframe.

Related

How to get browser and browser version used by a WebView using Swift

I would like to get the browser (e.g. Safari) and the browser version of the browser that is used in a WKWebView when it opens up an URL. Any help is greatly appreciated!
WKWebView doesn't "use a browser". WKWebView is the browser engine that is used by Safari. As a matter of fact, all web browsers on iOS are explicitly required to use WebKit framework, as per App Store Review Guidelines
2.5.6 Apps that browse the web must use the appropriate WebKit framework and WebKit Javascript.

Video seeking does not work in PWA (Progressive Web App)

html5 video player seeking does not work in PWA (Progressive Web App) as standalone APP.
Tested devices: Android and iOS.
When you accessing to the Web Page via Safari or Chrome it's working fine, but not as pwa standalone app.
What is the problem with that?
This is due to a gap in the spec which was recently fixed. If you're interested in the details, I wrote an article about it.
Once browsers update to the new spec, media will just work as expected. Here are the related tickets:
https://bugs.chromium.org/p/chromium/issues/detail?id=847428
https://bugzilla.mozilla.org/show_bug.cgi?id=1465074
https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/17689699/
https://bugs.webkit.org/show_bug.cgi?id=186050
In the meantime, everything should work as expected if you use CORS:
<video crossorigin></video>
…although this requires the server to support CORS.

Building app, mobile web app and desktop web app using Ionic

We will develop an app that we would like to distribute in through the following channels:
Android and iOS apps through Google Play and iTunes (the app will
use notifications extensively and presence in Google Play and App store is required)
Web app to run in web browsers on mobile devices
Web app to run in web browsers on laptop and desktop computers. We would like to support Chrome, Internet Explorer (starting from IE9),
Firefox and Safari browsers.
Our understanding is that Ionic is developed targeting primarily 1. and that the web apps in 2. and 3. above are not really what Ionic is intended for. We have looked around to try to understand if Ionic likely works for 2. and 3. and also made some quick tests ourselves.
From one of the links at the end: "Your webapp will run in desktop browsers yes, as it is made of html, css and javascript. The phonegap specific javascript calls (accelerometer, compass, file, etc) won't. Basically, if you stick to standard yes you will be able to port relatively easily your app to most browser, the job at this point being mostly a work of theming."
From another one: "I do know that FireFox is simply not supported. I don't know how well Ionic works in IE X."
To try it out we have built a limited version of our app in Ionic. From what we can see the app works for 1, 2 and 3. For example, it runs without issues on FireFox that is mentioned as not supported in the quote above. This means that to us it looks like the first quote saying that the web app will work in desktop browsers is correct.
I understand that this is a fairly generic question and might be hard to answer, but since we have found contradicting information when looking we are trying to understand more before making a decision.
Any feedback would be appreciated.
Thanks,
Markus
Is it a good idea to use ionic to build mobile web version of a website?
Can Ionic Framework run in desktop web browser like Chrome, Mozilla, IE9+?
http://forum.ionicframework.com/t/ionic-components-on-ie/1826
Phonegap web app in regular desktop browsers
http://ionicframework.com/docs/overview/#css-sass
Ionic is tested for mobile only. Internet Explorer for example is not tested and does not properly handle a number of features in Ionic. Desktop browsers act differently than mobile browsers.
Ionic is focused on building native/hybrid mobile apps rather than
mobile websites.
As such, our browser support tends to be whatever Web View API is
available to native apps on a given platform. For Ionic 1.1.0
"xenon-xerus", that means UIWebView for iOS 7+, and Android 4.1 and
up. Windows Phone and FirefoxOS support is on our roadmap.
If it's cheaper for you to test everything on all different desktop browsers than to develop a version for it sharing the same controllers and services --- go ahead but it won't come "out of the box".
Also, I recommend looking at Electron to build desktop apps from webapps.
ionic is targting mobile apps only , but you can develop your desktop app using node webkit and angular material for example and share some code between your apps

Jquerymobile HTML5 Iphone App Add to Home screen

I'm creating a Mobile App with JQM and JSP I'm using Bookmark bubble to do this, but I just want to ensure I understand what is happening behind the scenes here.
Is the static HTML generated by my JSP saved locally on the iPhone?
Does clicking on the APP always get fresh info from my online server or does it cache?
I'm assuming it still uses Safari to render? And just hides the toolbar etc?
If instead of hosting this online, I packaged it as an Apple App and it went on App store,
would the device still use safari to render it?
Thanks!
Documentation is at: https://developer.apple.com/library/content/documentation/iPhone/Conceptual/SafariJSDatabaseGuide/OfflineApplicationCache/OfflineApplicationCache.html
It's possible to cache the page(s) locally.

Why might cache-manifest fail to get mobile Safari to cache site while working as expected on desktop?

I'm playing around with a simple web app locally, and can't quite figure out why it is not caching correctly on the iPhone. I am serving a .manifest file with the correct MIME-type, and the site works perfectly fine with my local server turned on or off on desktop Safari, Chrome and Firefox. It is only mobile Safari that is failing to cache the site. Any ideas why this might be?
It seems to be an iOS bug.
I found out that mobile safari will always run into an application caching error if you have at least one web view opened and the you clear the browser cache. I think that clearing the browser cache will destroy the cache database. All accesses to the cache database will then fail. It seems that the browser creates this database only on startup.
To get the application cache working again close all safari views and finally close the browser by returning to the home screen. Now applicaton caching should working. Some mobile devices also requires switching on and off.
If you know a methode to detect this situation let me know it, please.
I had a similar issue but Safari and iPhone were both NOT working whilst IE and Firefox were working. The reason was complex. One was a misspelling of the word "manifest" in the HTML tag. Silly mistake and very frustrating that IE and FF still worked offline. The other issue was that I was using default.asp as the main page of my app and not including this in the manifest.
My app was mydomain.com/myapp/ and thus the browser never saw the "default.asp". Also, according to the HTML5 spec, the main page need not be in the manifest but apparently Safari sees that a little differently...
I can confirm that the bug is also present on iPAD running iOS 4.3.
I spent quite some time to make the offline application cache work on iPad. I can confirm that the workaround mentioned in the previous post works.