webview_plus 0.8.4

webview_plus: ^0.8.4 copied to clipboard

• Custom URL Scheme (app-assets://): Introduced a custom URL scheme handler (WKURLSchemeHandler) to safely intercept local asset requests without conflicting with WebKit's security policies.
• MIME Type Resolver: Added a helper function (getMimeType) in the Swift handler to map file extensions (such as .jpg, .png, .css, .js) to their respective MIME types, ensuring the WebView correctly renders the intercepted resources.

[Changed] #

• Native URL Scheme Registration: Replaced the private, non-functional _setURLSchemeHandler:forURLScheme: method (which attempted to override http/https) with the official setURLSchemeHandler(_:forURLScheme:) method targeting the new app-assets scheme.
• Dart HTML Resource Paths: Updated the local image path conversion in the Flutter layer to replace the restricted file:// protocol with the new custom app-assets:// prefix.
• Resource Loading Logic: Rewrote the Swift resource handler to capture app-assets:// URIs, dynamically convert them back to local file system paths (file://), read the data securely from the disk, and stream it back to the WKWebView.

[Fixed] #

• onLoadResource Silent Failures: Fixed a limitation where WKWebView silently ignored or blocked custom scheme handlers bound to standard web protocols (http, https, file), preventing resource interception events from triggering.

• Remove the "Picture in picture" in macOS to remove the build failed.

Fixed #

• Linux: fixed a critical bug where opening a WebviewWidget could corrupt the Flutter engine's OpenGL rendering context, breaking rendering across the entire app — not just the webview. Depending on timing, this ranged from a black band covering all Flutter widgets to a complete engine failure (FlutterEngineRunTask repeatedly returning kInvalidArguments, nothing rendering at all). Root cause: the plugin reparented the Flutter FlView into a new GtkOverlay after the engine had already bound its GL resource context to the view's original GdkWindow; tearing that window down and rebuilding it mid-session invalidated the context.

Changed — action required on Linux #

• The GtkOverlay used to host native Webviews must now be created up front in linux/my_application.cc, before the engine starts rendering, instead of being assembled at runtime by the plugin. This is what actually fixes the bug above. See the new Setup on Linux section for the exact snippet to add.
• The plugin's previous runtime fallback (reparenting the FlView on first Webview creation) is kept only as a safety net for projects that haven't applied this change yet, and is no longer the recommended path — it remains susceptible to the rendering bug described above.

Fixed #

• Android: fixed a major scroll/rendering performance regression introduced by the transparent-background fix in a previous release. When transparentBackground: true was set, the WebView could get stuck permanently in LAYER_TYPE_SOFTWARE (CPU rendering) instead of switching back to LAYER_TYPE_HARDWARE after the page finished loading, causing persistent jank during scrolling and animations. The hardware layer switch is now only delayed by a couple of frames after onPageFinished (enough to avoid the black-flash artifact on the first transparent composite), then restored as before.
• Android: initial layer type is no longer forced to LAYER_TYPE_SOFTWARE at WebView creation for opaque backgrounds, avoiding an unnecessary software-rendered frame before the first hardware composite.
• Android: fixed unnecessary WindowInsets rebuild/redispatch on every touch interaction when disableKeyboardResize: true is set. The listener now only rebuilds and redispatches insets when the IME inset is actually non-zero, instead of doing so unconditionally — this was causing the engine to resend viewport metrics on every tap, adding visible input latency between touch and render.

• Announcement: Linux and Web platforms are now fully functional and supported! 🚀
• Feature: injectJsData / injectCssData (injecting raw JS/CSS directly into the active page) are now functional across all 7 platforms (Android, iOS, macOS, Windows, Linux, Web). Previously, only file/asset-based injections (injectJavascriptFileFromUrl, injectCSSFileFromUrl, etc.) worked natively.
• Feature: Added WebviewWidget.initialCss to automatically reinject raw CSS on every page load (initial or following navigation) across all 7 platforms.
• Feature: Added WebviewSettings.allowFileAccessFromFileURLs and WebviewSettings.allowUniversalAccessFromFileURLs (iOS/macOS). Enable these if a page loaded from the local disk (loadFile/loadFlutterAsset) fails to fetch other local files via fetch/XHR—the most common cause of local files "not opening" on these two platforms.
• Feature: Added WebviewCacheManager (clearCache(), clearCookies(), clearAllData()) to clear HTTP cache, cookies, or all web data across the application's Webviews, independent of any active on-screen instance. Available across all 7 platforms.
• Feature: Added WebviewPlusController.setWebContentsDebuggingEnabled() to enable/disable remote inspection (Chrome DevTools/Safari Web Inspector) globally for all current and future Webviews in the app, unlike WebviewSettings.isInspectable which applies to a single instance.
• Feature: Extended custom scrollbar coloring (previously Windows-only, see DesktopScrollbarThemeMode) to macOS and Linux, as both expose the same ::-webkit-scrollbar* CSS pseudo-elements as WebView2/Chromium.
• Fix (macOS): disableContextMenu and disableLongPressContextMenuOnLinks previously blocked the context menu by clearing it after creation (willOpenMenu), which could sometimes leave an empty menu visible (specifically the word selection menu). The menu is now prevented from building ahead of time (menu(for:)), fixing the residual empty menu when right-clicking selected text.
• Fix (macOS): Fixed a bug where selectionTextColor was being read from the wrong settings key (selectionHandleColor, which is Android-specific) and had no actual effect.
• Improvement: Significantly expanded WebviewSettings coverage on macOS to match iOS/Android parity: mediaPlaybackRequiresUserGesture, initialBackgroundColor, disablePrinting (JS + Cmd+P shortcut), allowsPictureInPicture, cacheEnabled, forceDarkMode (via NSAppearance, forcing prefers-color-scheme: dark), and hideNativeScrollbars (via CSS injection, now shared with Linux).
• Feature: Added WebviewInitialData to WebviewWidget for advanced raw data and HTML loading with mimeType, encoding, baseUrl, and androidHistoryUrl across all platforms (Windows ignores baseUrl due to native WebView2 limitations).
• Feature: Added comprehensive Windows scrollbar theming support via DesktopScrollbarThemeMode (auto, light, dark, custom, and hidden modes). Supports runtime updates of track/thumb colors, width, and hover states.
• Feature: Significantly expanded WebviewSettings with a suite of new cross-platform controls:
  • cacheEnabled (All) — Toggle session and HTTP caching.
  • incognito (All) — Run webview in private/incognito profile.
  • applicationNameForUserAgent (All) — Easily append a custom app name to the default User Agent.
  • textZoom (Android) — Adjust text sizing percentages.
  • minimumFontSize (Android/iOS/macOS) — Enforce a minimum readable font size.
  • allowsInlineMediaPlayback (iOS/macOS) — Native control over inline video.
  • allowsPictureInPicture (iOS/macOS) — Allow PiP mode on supported native media.
  • javaScriptCanOpenWindowsAutomatically (All) — Prevent/allow window.open calls.
  • geolocationEnabled (Android) — Native hardware geolocation toggle.
  • thirdPartyCookiesEnabled (Android) — Manage cross-site cookie settings.
  • forceDarkMode (Android) — Explicitly force dark mode mapping.
  • overScrollMode (Android) — Control native overscroll glow behavior.
  • bounces (iOS/macOS) — Control scroll bouncing physics.
  • initialScale (Android) — Set default viewport zoom scale.
  • hideNativeScrollbars (All) — Easily hide default scrollbars.
  • safeBrowsingEnabled (Android) — Toggle Google Safe Browsing checks.
  • allowMixedContent (Android) — Allow loading HTTP content inside HTTPS pages.
• Change: Changed getHtml to return a formatted HTML string (with proper indentation and newlines) on Windows.
• Feature: Added onFontsIsLoaded callback on Windows, Android, and macOS.
• Dependency: Updated to use the new androidx.webkit:webkit:1.16.0 dependency on Android.

• Fixed Windows WebView bridge initialization: Isolated user scripts in try-catch blocks and optimized execution order to prevent custom scripts from blocking addJavaScriptHandler.

• Add selectionTextColor setting on Android and iOS.
• Add selectionHandleColor setting on Android.
• Add disableKeyboardResize setting on Android and iOS to prevent WebView from resizing when the virtual keyboard appears.
• Add initialUserScripts setting to inject JavaScript code into pages on Android, iOS, and macOS.
• Add disabledDefaultContextMenuItems setting to individually disable default native context menu items on Android and iOS.

• Add onDOMContentLoaded callback on IOS, MacOS and Linux.
• Add mouse cursor change (onCursorChanged) support on Windows (the diagonal resize cursors).
• Android and Windows bug: A white screen appears while the WebView is loading, even when transparency is enabled.
• Add initialBackgroundColor setting across all platforms to eliminate the white screen/flash of unpainted content during initialization and loading.
• Replace useHybridComposition with AndroidPlatformViewType enum, featuring automatic fallback to Hybrid Composition (initExpensiveAndroidView) on devices below Android SDK 23.

• Fixed the onDOMContentLoaded callback not being called on all platforms.

• Fixed a critical Android WebView crash by allowing nullable arguments (String?) on JavaScript-to-Kotlin bridges to gracefully handle empty page lifecycles.

• Bug in the evaluateJavaScript function on macOS and iOS causing a crash.
• Remove the PrivacyInfo file in macOS for remove the warning.

• Android: switch to initSurfaceAndroidView (Texture Layer Hybrid Composition) by default on API 23+, replacing the old choice between Virtual Display (janky scroll) and Hybrid Composition (janky Flutter animations around the webview). Native scroll and Flutter transitions/dialogs are now both smooth. Falls back automatically to the previous behavior on API < 23.
• Android: smoother native scrolling — disabled the overscroll glow effect (overScrollMode = OVER_SCROLL_NEVER) and enabled nested scrolling (isNestedScrollingEnabled).
• Android: faster first paint — enabled useWideViewPort and loadWithOverviewMode to avoid a desktop-then-mobile relayout on pages without a proper viewport meta tag.
• Android: explicit cacheMode = LOAD_DEFAULT to make sure standard HTTP caching is honored, enabling faster subsequent loads.
• Added WebviewPlusPreloader, a new API to speed up webview loading:
  • WebviewPlusPreloader.warmUp({int count = 1}) pre-creates WebView engine instances in the background, moving the one-time Chromium engine initialization cost off the critical path of the first visible webview.
  • WebviewPlusPreloader.preloadUrl(String url) loads a URL in an invisible, disposable webview ahead of time to warm the shared HTTP cache, speeding up the real webview's load of the same URL later.
  • Both are no-ops on non-Android platforms.
• Rename the evaluateJavaScript setting in controller to evaluateJavascript to match with the other webview in flutter.

Windows changes:

• Navigation: Fixed an issue where the canGoBack and canGoForward state properties were not functioning.
• Focus: Fixed the WebView hijacking focus and causing the main Flutter window to lose active focus when clicked.
• Cursor: Fixed the mouse cursor failing to adapt (e.g., changing to a text-selection cursor) when hovering over web content.
• Context Menu: Fixed the right-click context menu appearing misaligned/offset when running the application in windowed mode.

Android changes:

• Use initSurfaceAndroidView or initHybridAndroidView when is available (API 23+).
• Add support for Android 12's new "Hybrid Composition++" mode (requires API 34+).

• Add WebviewEnvironment for Windows (userDataFolder)

• Update onLoadStart / onLoadStop / onReceivedError / onNavigationRequest and remove shouldOverrideUrlLoading (now use onNavigationRequest only)
• Add onDOMContentLoaded / onWindowFocus / onWindowBlur

• Initial Commit