尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證A Flutter plugin that allows you to add an inline webview, to use a headless webview, and to open an in-app browser window.
翻譯準備中
取自儲存庫 README
正在載入完整 README。
檢視完整 README ↗A Flutter plugin that allows you to add an inline WebView, use an headless WebView, and open an in-app browser window.
This is a community-driven fork of flutter_inappwebview focused on active maintenance, stability, and modern platform support.
Thanks to ZikZak AI for sponsoring this project!
ZikZak AI is an AI-Powered Price Comparison app that you scan barcodes, and discover amazing savings instantly. Your personal shopping assistant that never sleeps.
Documentation | Pub.dev | API Reference | Changelog
Add zikzak_inappwebview to your pubspec.yaml:
dependencies:
zikzak_inappwebview: ^6.3.2
| Platform | Minimum Version | Notes |
|---|---|---|
| Flutter | 3.10.0+ | |
| Android | API 24+ | Android 7.0+ |
| iOS | 15.0+ | |
| macOS | 12.0+ | |
| Windows | 10+ | Requires WebView2 Runtime |
| Linux | Requires WebKitGTK 2.40+ | |
| Web | Any |
On the Flutter 3.47.x stable line, iOS platform views — including InAppWebView — can make the Flutter content painted after them vanish from the frame ("rendering layer confusion"): an AppBar turns invisible, a modal bottom sheet's footer and the list items below a WebView card are not drawn. Upgrading from 3.44.x to 3.47.2 triggers it; the same app renders correctly on 3.44.x. It reproduces with Impeller disabled, so it is not an Impeller rasterizer bug.
This is an engine regression in Flutter's texture-layer hybrid composition (TLHC) overlay path, tracked upstream in flutter/flutter#193363 (triaged engine / platform-views, c: regression). It is not a plugin code defect: the on-device mitigation matrix in .specify/bugs/flutter347-platformview-rendering/fix.md (§ Mitigation matrix) leaves the artifact unchanged for every candidate tested.
The symptom, the evidence and the workarounds are documented once, in the package README's Known Issues section — that copy is canonical, so read and edit it there.
Check out the online documentation for comprehensive guides and examples.
import 'package:zikzak_inappwebview/zikzak_inappwebview.dart';
// ... inside your widget tree
InAppWebView(
initialUrlRequest: URLRequest(url: WebUri("https://flutter.dev")),
onWebViewCreated: (controller) {
// Controller is ready!
},
)
Simply replace the import:
// Before
import 'package:flutter_inappwebview/flutter_inappwebview.dart';
// After
import 'package:zikzak_inappwebview/zikzak_inappwebview.dart';
The API is nearly identical. Version 4.x.x corresponds to upstream 6.x.x. This fork has resolved all 156+ upstream issues and added critical fixes for SPM migration, Web platform support, Windows WebView2, and OEM device compatibility.
Note — JavaScript bridge global. The injected JavaScript bridge global is
window.zikzak_inappwebview(notwindow.flutter_inappwebview). After migrating, call handlers viawindow.zikzak_inappwebview.callHandler(...). TheflutterInAppWebViewPlatformReadyevent name is unchanged.
Contributions are welcome! If you find a bug or have a feature request, please open an issue.
This project is licensed under the Apache License 2.0 - see the LICENSE file for details.