![]() ![]() The default user data folder (UDF) location varies per platform. Start a new WebView2 host app session, specifying a new custom UDF location. If the host app is installed per-user, each UDF is unique to a user, if not otherwise specified. This depends on how your host app configs the UDF.Ī UDF can be either per user, if the app was installed per-user. It's possible for your host app to overlap them, by specifying a custom UDF location. There is at least one UDF per app WebView2 session. There's only 1 active UDF per WebView2 session. How many UDFs are created?Įach instance of a WebView2 control is associated with a user data folder (UDF).Įach WebView2 session must have a UDF. The UDF is created on startup of the WebView2 host app, if the UDF doesn't exist. The UDF is created in the default UDF location for the platform, or if your host app specifies a custom UDF location, the UDF is created in the custom UDF location. The user data folder (UDF) is created for your WebView2 host app by the WebView2 control. ![]() The above types of data are listed as enum members in the CoreWebView2BrowsingDataKinds Enum. Includes payment data.ĭata stored by the IndexedDB DOM feature.ĭata stored by the Web SQL database DOM API. This excludes password information and includes information such as names, street and email addresses, phone numbers, and arbitrary input. New site data types may be added to this data kind in the future. This browsing data kind includes the data kinds AllDomStorage and Cookies. This browsing data kind includes the data kinds AllSite, DiskCache, DownloadHistory, GeneralAutofill, PasswordAutosave, BrowsingHistory, and Settings.Īll site data, now and future. New profile data types may be added to this data kind in the future. This does not delete account-scoped data like passwords but will remove access to account-scoped data by signing the user out. Profile data that should be wiped to make it look like a new profile. This browsing data kind is inclusive of FileSystems, IndexedDb, WebSql, CacheStorage. Type of dataĭOM storage data, now and future. WebView2 apps use user data folders (UDFs) to store browser data, such as cookies, permissions, and cached resources. This can result in slowdowns, crashes, or loss of data. The custom UDF location must have appropriate Read/Write permissions for the WebView2 app runtime.Īvoid storing user settings on a network drive. If you specify a custom UDF location, it should meet the following requirements: If your app has specific needs, you can specify a custom UDF location. This works well on some platforms, but not others. WebView2 creates the UDF in the default location for the platform, or in the custom UDF location that your host app explicitly specifies.īy default, WebView2 creates a UDF in the default location for the particular platform. The directory path that your WebView2 host app specifies where WebView2 will create the user data folder. The directory path where WebView2 creates the UDF if you don't specify a custom UDF location.Ī custom location for the user data folder. The default directory path of the user data folder. The directory path of the user data folder. WebView2 apps use user data folders to store browser data, such as cookies, permissions, and cached resources.Ī folder that WebView2 creates to store browser data, such as cookies, permissions, and cached resources. The user data folder (UDF) is a folder stored on the user's machine, that contains data related to the host app and WebView2. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |