v1.0.0

⚠️ Breaking change — migrating from pre-Nucleus / Wry builds

1. Classpath / package — rename imports and package references:

   • io.github.kdroidfilter.webview.* → dev.nucleusframework.webview.*
   • Maven coordinates: io.github.kdroidfilter:… → dev.nucleusframework:composewebview

2. Desktop is Tao-only — the old Wry desktop backend is removed. Desktop WebView requires the Nucleus Tao backend (NativeView):

   • App entry: nucleusApplication(backend = NucleusBackend.Tao) { … }
   • Dependencies: Nucleus application + decorated-window-tao (Swing/Compose Desktop without Tao will not host the WebView)

   Why Tao? Native WebViews are opaque platform surfaces. Tao’s NativeView embeds them in the same window stack as Compose, so you can draw Compose UI on top of the WebView (toolbars, dialogs, loading overlays, chrome) instead of fighting a separate HWND/GTK child. You also get the rest of Tao’s desktop stack (decorated window, title bar, input routing, multiplatform windowing) in one path.

Android, iOS and WasmJs keep the same API shape; only the package and Maven group change.

See the README migration note for details.

What's Changed

• fix(wry): WryCookieManager.getCookies always throw WrongThread exception on Windows by @KRTirtho in #38
• Update compile and target SDK versions to 36 to fix build of androidx.navigationevent by @dd10-e in #40
• Fix for #43; Added Possibility to write tests for the WebView by @DrUlysses in #44
• Add domStorageEnabled to AndroidWebSettings by @dd10-e in #39
• Migrate to NucleusFramework: Tao/NativeView desktop WebView (Linux) and drop Wry by @kdroidFilter in #49

New Contributors

• @KRTirtho made their first contribution in #38
• @dd10-e made their first contribution in #40

Full Changelog: v1.0.0-beta-02...v1.0.0