You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Applying additional_browser_args, empty or not to any window builder during app_setup.
[2024-09-26][06:10:44][tauri_runtime_wry][ERROR] failed to create webview: WebView2 error:
WindowsError(Error { code: HRESULT(0x8007139F), message: "The group or resource is not in the correct state to perform the requested operation." })
I create few windows during app setup, main, popover etc, and notice bugged behaviour when additional_browser_args applied to any on them.
For example, if use additional_browser_args("--enable-features=msWebView2EnableDraggableRegions --disable-features=ElasticOverscroll"), or .additional_browser_args("") to main window builder - i get HRESULT(0x8007139F) on any webview create from javascript frontend (ts/react).
But other windows, created from rust frontend works.
If i apply additional_browser_args to my secondary, popover window, webviews creates from js successfully, but interaction with popover webview, created from rust backend causes panic.
Applying additional_browser_args for both, main and popover window cause only failed to create webview: WebView2 error fro js, without panic.
i get HRESULT(0x8007139F) on any webview create from javascript frontend (ts/react).
But other windows, created from rust frontend works.
That part doesn't make sense to me tbh. It's not documented properly but every different additional_browser_args config also need a different data_directory config (so as long as the browser args are the same, they can share a directory). If you don't do this you get the "not in the correct state" error.
i get HRESULT(0x8007139F) on any webview create from javascript frontend (ts/react).
But other windows, created from rust frontend works.
That part doesn't make sense to me tbh. It's not documented properly but every different additional_browser_args config also need a different data_directory config (so as long as the browser args are the same, they can share a directory). If you don't do this you get the "not in the correct state" error.
I mean that from frontend webview created without any arguments, there is no such property new WebviewWindow(label, {...}, but if any window with additional_browser_args builded in rust, i get this error.
That is, in order for this error not to occur, you must also specify data_directory when specifying additional_browser_args in rust builder?
FabianLars
changed the title
[bug] additional_browser_args to window builder causes failed to create webview: WebView2 error
document that changing additional_browser_args require changing data_directory if multiple webviews will be opened
Sep 26, 2024
Describe the bug
Applying
additional_browser_args
, empty or not to any window builder during app_setup.I create few windows during app setup, main, popover etc, and notice bugged behaviour when
additional_browser_args
applied to any on them.For example, if use
additional_browser_args("--enable-features=msWebView2EnableDraggableRegions --disable-features=ElasticOverscroll")
, or.additional_browser_args("")
to main window builder - i getHRESULT(0x8007139F)
on any webview create from javascript frontend (ts/react).But other windows, created from rust frontend works.
If i apply
additional_browser_args
to my secondary, popover window,webviews
creates from js successfully, but interaction with popover webview, created from rust backend causes panic.Applying
additional_browser_args
for both,main
andpopover
window cause onlyfailed to create webview: WebView2 error
fro js, without panic.Reproduction
No response
Expected behavior
No response
Full
tauri info
outputStack trace
Additional context
No response
The text was updated successfully, but these errors were encountered: