[bug] Additional WebviewWindow Shows Blank Screen When Using additionalBrowserArgs in tauri.conf.json

[pedrohjp]

Describe the bug

Every webviewWindow I try to create ends up as a frozen white screen—I can't even close it... In this case, it's an additional webviewWindow; the idea is to have a secondary window in my app for another functionality. The main window of my app is working just fine.

I'm creating it like this:

// Create the window with basic settings
const window = new WebviewWindow(tab.id, {
  url: '/window-content',
  title: tab.title,
  width: 800,
  height: 600,
  center: true,
  focus: true,
});

But the issue is being caused by the additionalBrowserArgs property in the tauri.conf.json file:
"additionalBrowserArgs": "--ignore-certificate-errors"

I've tested it—it has nothing to do with that flag specifically. Even if I leave it as an empty string, the issue still occurs. But if I remove that line entirely, the app works perfectly again... The window opens and displays the content as expected! Any idea how to fix this?

The new webviewWindow is so bugged that i cant even open the terminal to see any errors...

Reproduction

No response

Expected behavior

No response

Full tauri info output

[✔] Environment
    - OS: Windows 10.0.26100 x86_64 (X64)
    ✔ WebView2: 134.0.3124.93
    ✔ MSVC: Visual Studio Community 2022
    ✔ rustc: 1.84.0 (9fc6b4312 2025-01-07)
    ✔ cargo: 1.84.0 (66221abde 2024-11-19)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 22.14.0
    - npm: 10.9.2

[-] Packages
    - tauri 🦀: 2.4.0
    - tauri-build 🦀: 2.1.0
    - wry 🦀: 0.50.5
    - tao 🦀: 0.32.8
    - @tauri-apps/api : 2.4.0
    - @tauri-apps/cli : 2.4.0

[-] Plugins
    - tauri-plugin-opener 🦀: 2.2.6
    - @tauri-apps/plugin-opener : 2.2.6

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: React
    - bundler: Vite

Stack trace

Additional context

No response

[FabianLars]

Do you see any errors in the terminal? This sounds like it's caused by the requirement of needing a different data_directory if additionalBrowserArgs changes, but that should print errors or panic.

the data_directory config and a runtime version of additional_browser_args are only available on the rust side so the js webviewwindow api would not work here

[pedrohjp]

There are no problems in the terminal, not in the vscode terminal or the main webview JS terminal... The only reason i need to use additionalBrowserArgs is to disable certificate errors, maybe theres another way to do this

[pedrohjp]

Do you see any errors in the terminal? This sounds like it's caused by the requirement of needing a different data_directory if additionalBrowserArgs changes, but that should print errors or panic.

Actually, right now i saw that after i finish the process, hitting ctrl C in the terminal, thats the only way to close the app, i see that this message shows in the terminal, but only after closing the application:

[0329/101648.770:ERROR:window_impl.cc(122)] Failed to unregister class Chrome_WidgetWin_0. Error = 1411

[FabianLars]

There are no problems in the terminal, not in the vscode terminal or the main webview JS terminal... The only reason i need to use additionalBrowserArgs is to disable certificate errors, maybe theres another way to do this

Yeah, i still think it's what i said in my last message so you'll have to create that window on rust, or create it in tauri.conf.json but hidden via visible: false (it will consume some resources already that way)

Actually, right now i saw that after i finish the process, hitting ctrl C in the terminal, thats the only way to close the app, i see that this message shows in the terminal, but only after closing the application:
[0329/101648.770:ERROR:window_impl.cc(122)] Failed to unregister class Chrome_WidgetWin_0. Error = 1411

That's irrelevant (unrelated to the issue here) and actually not reallyyy an error.