Standardize document id

[chrmod]

Chrome documentation: https://developer.chrome.com/blog/extension-instantnav

Without explicit document ids, apis like webRequest and webNavigation are inaccurate.

Complexity comes from browser features like back-forward cache and prefetches and preloads.

[carlosjeurissen]

In similar fashion, would be good to specify the targetId concept. This seems similar to documentId but constant for a specific tab + frame combination. Linking targetIds with tabId, frameId and documentId would be very useful in regards with the debugger API. See:
https://issues.chromium.org/issues/450713296

In general it would be good to specify all the different types of ids used in the extension ecosystem.
windowId
groupId (tabgroups)
splitViewId
tabId
frameId
targetId
documentId
contextId

Ideally an extension would be able to get all the parent ids. IE, based on a contextId or documentId, get the windowId and tabId.

[Rob--W]

A problem that documentId resolves was described before in #8, which is considered addressed by documentId.

[Rob--W]

For completeness, Chrome's current set of APIs that support documentId (and in some cases parentDocumentId) is:

• webNavigation
• webRequest
• scripting (InjectionTarget of scripting.executeScript and scripting.insertCSS/removeCSS) (to do: allow just documentId without tabId - Proposal: scripting.executeScript without specifying tabId #91)
• userScripts.execute (specified in https://github.com/w3c/webextensions/blob/main/proposals/user-scripts-execute-api.md)
• extension messaging APIs:
  • runtime.MessageSender
  • tabs.sendMessage and tabs.connect
• runtime.getContexts() (specified in https://github.com/w3c/webextensions/blob/main/proposals/runtime_get_contexts.md)
• permissions.addHostAccessRequest and removeHostAccessRequest (specified in https://github.com/w3c/webextensions/blob/main/proposals/permissions-addHostAccessRequest-api.md)
• cookies.getPartitionKey (specified in https://github.com/w3c/webextensions/blob/main/proposals/hasCrossSiteAncestor.md)
• declarativeNetRequest.onRuleMatchedDebug
• (also declarativeWebRequest - but we don't care about this one; this is Chrome-only and MV2-only)

[Rob--W]

Firefox bug tracking documentId implementation: https://bugzilla.mozilla.org/show_bug.cgi?id=1891478