feat(windows): add with_profile_name for WebView2 multi-profile support

[jtbourke]

Adds WebViewBuilderExtWindows::with_profile_name so embedded webviews can opt into a named WebView2 profile, isolating cookies, storage, IndexedDB, and cache from the host app's default profile while sharing the same WebView2 environment/runtime.

Motivation

A common use case for wry (and Tauri downstream) is hosting an in-app browser tab alongside the main app webview. Without profile isolation, both share the unnamed default profile under the same user_data_folder, which means anything a user does in the embedded browser (signing into github.com, storing cookies, etc.) is mixed with the host app's own localStorage state. Profile-wide operations like clearing browsing data become unsafe because they touch the host app's storage as collateral damage.

with_data_directory (separate user_data_folder) is the existing workaround but it creates an entirely separate WebView2 environment with its own runtime/networking stack — which has historically caused OAuth/login-page regressions in apps that tried it (downstream report: Glint #2665).

Microsoft's recommended multi-profile pattern (https://learn.microsoft.com/en-us/microsoft-edge/webview2/concepts/multi-profile-support) is named profiles within a shared environment, which ICoreWebView2ControllerOptions::SetProfileName enables. This PR exposes it through wry.

Changes

• New profile_name: Option<String> field on the Windows PlatformSpecificWebViewAttributes.
• New trait method on WebViewBuilderExtWindows: with_profile_name<S: Into<String>>(self, name: S) -> Self.
• In create_controller, when a profile name is configured, call ICoreWebView2ControllerOptions::SetProfileName before CreateCoreWebView2ControllerWithOptions.

When with_profile_name is not called the behavior is unchanged — the webview uses the unnamed default profile, same as today.

Platform notes

This PR only touches Windows. macOS / iOS already have with_data_store_identifier for the equivalent functionality. A follow-up could add the Linux equivalent (a dedicated WebsiteDataManager directory) under a unified API name if there's appetite for that.

Naming-rule notes

WebView2 enforces profile-name rules (alphanumeric + ., _, -, space; up to 64 chars; cannot start or end with . or space). The doc-comment on with_profile_name mentions these constraints. The patch doesn't validate the string client-side — SetProfileName returns an error for malformed names, which is surfaced as a wry::Error at build time.

Related

• Closes Support for Browser Profiles (extension of Tauri issue #9285) #1321 (Support for Browser Profiles) — at least the Windows half.
• Tauri tracking issue: [feat] Support for Browser Profiles tauri#9285.

[github-actions]

Package Changes Through 2a081b9

There are 1 changes which include wry with minor

Planned Package Versions

The following package releases are the planned based on the context of changes in this pull request.

package	current	next
wry	0.55.1	0.56.0

Add another change file through the GitHub UI by following this link.

---

Read about change files or the docs at github.com/jbolda/covector

[Legend-Master]

Thanks! Could you also add a change file?

https://github.com/tauri-apps/wry/blob/dev/.changes/readme.md

Also you'll need to sign your commits for me to merge this

https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits

[Legend-Master]

Thanks!