Fabian-Lars

@Apogeum12 Unfortunately this is not something we can or want to do. Only if we absolutely have to. If we ignore that we already get enough complains for not supporting...

Would be a cool feature, but the upstream crate (https://github.com/PolyMeilex/rfd) doesn't support this yet, so it may take a while to implement.

@chhpt @gardc we're still mainly blocked by the feature freeze here. The audit process is coming to an end and with the 1.0 release being so close, we're completely focused...

@aliscie inject the app handle like this and it should work: https://tauri.app/v1/guides/features/command#accessing-an-apphandle-in-commands

i don't know anything about rust frontends tbh, but you don't need to inject the app_handle yourself, Tauri injects it for you (in that regard rust frontends are the same...

Can you try the same in Edge too? By default they should behave the same (even more than chrome + webview2) Also, what kind of GPU do you have? chrome...

The easiest way (and maybe only way, since the `with_webview` method probably triggers to late to inject these flags 🤔) to try that flag is via the `WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS` environment var.

Well for a temporary dev check you'd just set it in the terminal, for powershell it'd be `$env:WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS="--ignore-gpu-blacklist"`. For production (or for testing too i guess) you'd set that env...

funnily enough i did a really quick google search before posting this because i thought it was blAcklist and was confused as to why you wrote blOcklist. And even after...

`cargo tauri build` is only a thing after installing the tauri cli via `cargo install tauri-cli`, similar to the nom package.