MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Problem/Bug]: a problem with ICoreWebView2PermissionSettingCollectionView

Open
#5,252 0 comments 0 reactions 1 assignee View on GitHub

@prija-microsoft is already working on this.

Since May 23, 2025.

bug
Dominant language
PowerShell
Stars
526
Forks
67
PR merge metrics
No merged PRs in 30d

Description

What happened?

Seem have a problem with ICoreWebView2PermissionSettingCollectionView :

when a permission is read a second time with GetValueAtIndex :

here is my (test) code into the GetNonDefaultPermissionSettings callback :

UINT32 cnt(0);
CHECK_FAILURE(collectionView->get_Count(&cnt));	
if (cnt >= 1)
{
	wil::com_ptr<ICoreWebView2PermissionSetting> perm;
	CHECK_FAILURE(collectionView->GetValueAtIndex(0, &perm));
	
	wil::unique_cotaskmem_string org;
	CHECK_FAILURE(perm->get_PermissionOrigin(&org));	//ok, org is L"https://..."

	// read the permission another time cause problems :
	wil::com_ptr<ICoreWebView2PermissionSetting> perm2;
	CHECK_FAILURE(collectionView->GetValueAtIndex(0, &perm2));	// no error reported

	wil::unique_cotaskmem_string org2;
	CHECK_FAILURE(perm2->get_PermissionOrigin(&org2));	// <-- no error reported BUT org2 is L"" (empty string) now

	//also here perm2-get_PermissionKind		report no error but kind is wrong : 0 (unknown)
}

Is my code wrong ?

Importance

Moderate. My app's user experience is affected, but still usable.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

135.0.3179.98

SDK Version

1.0.2739.15

Framework

Win32

Operating System

Windows 10

OS Version

No response

Repro steps

try the code

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

No, this never worked

Last working version (if regression)

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.