[Problem/Bug]: Synchronizing Tab States with Extension Scripts in a Multi-tab Browser Developed with C# WebView2

What happened?

I have developed a multi-tab browser using C# WebView2. For each new tab created, a WebView2 instance is instantiated. Suppose I created 3 instances. In the extension script, I use:

chrome.tabs.query({active: true}, function(tabs) {
console.log(tabs);
});
to query the current active tab. Normally, it should only return the information of the active tab object, but the problem is that after executing the query, it returns 3 tab information entries that correspond to the previous 3 WebView2 instances, and all objects have the active property set to true, which is obviously incorrect.

Is this a bug in WebView2? Could anyone please help analyze this? Thank you very much.

I hope that when a new WebView2 instance is created, the display state of the WebView2 instance can be synchronized within the extension environment. The version of WebView2 I am using is 1.0.2535.41.

Importance

Important. My app's user experience is significantly compromised.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

1.0.2535.41

SDK Version

No response

Framework

WPF

Operating System

Windows 10

OS Version

No response

Repro steps

As long as multiple instances are created in C#, no matter which instance is visible, when querying through the extension script with:
chrome.tabs.query({active: true}, function(tabs) {
console.log(tabs);
});
it returns all instances and all of them have active set to true.

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

No repository files or tests are named. Start with the repro steps using multiple C# WebView2 instances and the chrome.tabs.query({active: true}) extension call, then compare the returned tab states with the visible instance. Done means determining whether this behavior is expected and documenting the supported synchronization or a confirmed WebView2 defect.