Refactor: Improve Desktop WebView loading and stability #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit introduces several improvements to the desktop WebView implementation:
e.printStackTrace()in thecatchblock ofDesktopWebView.loadHtmlfor better debugging of HTML loading errors.WebView.ktto use a commonwv.loadContent(content)call within theLaunchedEffectfor all content types, simplifying the logic.KCEFBrowserinstance is now recreated ifstate.contentchanges, ensuring the browser is correctly initialized for different content types (e.g., when switching from URL to File).WebViewFactoryParamforWebContent.Filenow passesparam.requestContexttocreateBrowser.state.webViewandwebViewJsBridge?.webVieware now set within aLaunchedEffectdependent ondesktopWebViewto ensure they are assigned after theDesktopWebViewinstance is fully created.java.io.FiletoFilefor consistency.