Ionic v3内置浏览器版本查询及iframe兼容调整咨询

Hey there! Let's break down your questions about Ionic v3's browser environment and that frustrating iframe issue you're facing:

Ionic v3 doesn't use a standalone browser—it relies on the native WebView component of the target platform (Android/iOS) to render web content, including your iframe. Here's the details by platform:

• Android:
  By default, Ionic v3 uses the system's built-in Android WebView, which is based on the Chrome engine. Its version is tied to the Android OS version:
  • For Android 7.0 (Nougat) and above: The WebView is updated independently via Google Play (same version as the Chrome browser installed on the device).
  • For Android 6.0 and below: The WebView is part of the system firmware, so its version is fixed to the OS release's bundled Chrome version.
• iOS:
  Ionic v3 defaults to using WKWebView (via the cordova-plugin-wkwebview-engine plugin) for better performance and modern web standards support. WKWebView's version is directly tied to the iOS system version—for example, iOS 14 includes WKWebView matching Safari 14's engine, iOS 15 matches Safari 15, etc. Older Ionic v3 setups might have used UIWebView, but that's deprecated and not recommended.

You can't "modify" the native WebView version directly, but there are workarounds depending on your platform:

• Android Options:
  1. Prompt users to update their WebView: For Android 7.0+, ask users to update the Android System WebView (or Chrome browser) via Google Play—this will get them the latest compatible engine version.
  2. Use the CrossWalk WebView plugin: You can integrate cordova-plugin-crosswalk-webview into your Ionic v3 project. This plugin packages a fixed version of the Chromium engine directly into your app, so it doesn't depend on the device's system WebView. While CrossWalk is no longer maintained, it's a viable option for older projects like Ionic v3 to ensure a consistent, modern engine version. Keep in mind this adds ~20-30MB to your app's size.
• iOS Options:
  1. Ask users to update iOS: Since WKWebView's version is tied to iOS, the only way to get a newer engine is to have users update their device to a newer iOS version that meets the external resource's browser requirements.
  2. Request compatibility from the external resource: If updating iOS isn't feasible for your user base, reach out to the team managing the external resource and ask if they can add support for older WKWebView versions (common in enterprise or legacy setups).

Bonus Tip #

If possible, consider alternative approaches to using an iframe—like integrating the resource's API directly into your app. This avoids relying on the WebView's compatibility with the external site's browser checks entirely.

内容的提问来源于stack exchange，提问作者Fabricio