Compatibility
Current Baseline
Section titled “Current Baseline”| Package | Version |
|---|---|
webview_all |
1.2.0 |
webview_all_windows |
1.2.0 |
webview_all_linux |
1.2.0 |
webview_all_ohos |
1.2.0 |
webview_all_web |
1.2.0 |
webview_flutter_platform_interface |
^2.15.1 |
webview_flutter_android |
^4.12.0 |
webview_flutter_wkwebview |
^3.25.0 |
| Flutter SDK | >=3.35.0 |
| Dart SDK | ^3.9.0 |
Platform Baseline
Section titled “Platform Baseline”| Platform | Support | Implementation |
|---|---|---|
| Android | API 24+ | WebView |
| iOS | 13.0+ | WKWebView |
| macOS | 10.15+ | WKWebView |
| Windows | Win10 1809+ | WebView2 |
| Linux | webkit2gtk-4.1 | WebKitGTK |
| OHOS | API 12+ | ArkWeb |
| Web | Any | js-interop |
Maintenance Rules
Section titled “Maintenance Rules”When upgrading webview_flutter_platform_interface:
- Compare new methods on the controller, delegate, widget, cookie manager, and platform factory.
- Every platform package must implement them explicitly.
- Prefer a real native implementation when the engine exposes one.
- Use
UnsupportedErrorwhen a feature cannot be provided. - Use no-op only for registration-style APIs protected by capability checks.
- Update the capability matrix and platform API documentation.
- Run format, analyze, tests, and publish dry-run before release.
Release Order
Section titled “Release Order”Publish child platform packages first, then publish the main package after pub.dev can resolve them:
webview_all_windowswebview_all_linuxwebview_all_webwebview_all_ohoswebview_all