[Feature]: [Extensions] Tab ID Mapping

[RendijsSmukulis]

Describe the feature/enhancement you need

Currently there is no easy way we have found to map the tab ids returned by chrome.tabs.query and similar chrome extension APIs to WebView2 instances in our native app tabs. That is, we have no way to know what tab is being referenced in our app when chrome.tabs.query returns "tabId = 1". A way to either find the current tab id of a WebVIew2 instance, or a way to provide the tab ID as the webview2 is created (or some other mechanism to map chromium internal tab ids with our app tab ids) would be extremely useful.

The scenario/use case where you would use this feature

For any situation where native and extension code interops and the context is tabs (e.g. reimplementing the behaviour of chrome.tabs.query), the extension and native code needs to agree which tab is which - hence there is a need for some way to map from native tabs/webview2 instances to the tab ids as seen by extensions.

How important is this request to you?

Critical. My app's basic functions wouldn't work without it.

Suggested implementation

No response

What does your app do? Is there a pending deadline for this request?

No response

AB#46892713

[sandeepchads]

Hi - I am reviewing some of the GH issues and feature requests opened. Wanted to clarify whether this is still an ask? While this continues to be low priority on our backlog, I also wanted to paraphrase my understanding of the issue.

Using native code, you have created few tabs and when extensions etc. operate on one of these tabs for example let's say I run an adblocker and it blocks ads on tab 1, you get a response called ad blocker blocked 17 ads on tab 1. However, you are unable to map tab = tab1 to your native tabs.

If my understanding is correct, I have 2 questions:

1. How are you solving this problem now? Do you have a work around?
2. What scenario would this light up? Basically, what functionality is not working if this mapping were not available.