fix: add cdp.resolveRealm command

[jrandolf-2]

cdp.resolveRealm resolves a realm ID to an executionContextId.

This is needed for Puppeteer to adopt nodes from ARIA queries.

This is a workaround for https://crbug.com/326258571

[OrKoN]

I wonder if instead we should accept realm in BiDi+ and automatically replace it with an execution context id. @sadym-chromium WDYT?

[jrandolf-2]

I wonder if instead we should accept realm in BiDi+ and automatically replace it with an execution context id. @sadym-chromium WDYT?

I think that's pretty clever. +1

[OrKoN]

Please update title/description

[sadym-chromium]

@jrandolf can you please elaborate a bit the original issue? Why do you need DOM.resolveNode CDP command in BiDi mode? Maybe you have a Puppeteer github issue link?

[sadym-chromium]

realm in BiDi+

If Puppeteer in BiDi needs to be aware of the CDP executionContextId, we can add a BiDi+ command cdp.resolveRealm:

CdpResolveRealmCommand = {
   method: "cdp.resolveRealm",
   params: CdpResolveRealmParameters,
}

CdpResolveRealmParameters = {
   bidiRealm: script.Realm,
}

CdpResolveRealmResult = {
   cdpExecutionContextId: text,
}

We already have CDP.getSession for the very same reason.

[OrKoN]

@sadym-chromium it’d be nice to avoid many round trips to support a11y queries over bidi+

[sadym-chromium]

@sadym-chromium it’d be nice to avoid many round trips to support a11y queries over bidi+

In case of puppeteer + mapper, this will be an internal call, without a roundtrip to the browser. But I'm not sure what is the specific scenario this is required to

[OrKoN]

@sadym-chromium it would be more problematic when if we start supporting chromedriver. Also, it's not always desirable to make an async call (due to potential races). I don't have a strong preference for either way.

getSession was already a bit problematic since we need to have it at the time of the Frame/Page construction and that is synchronous. Currently, we trigger it in the constructor without awaiting so it could be prone to flakiness.

[jrandolf-2]

@sadym-chromium it’d be nice to avoid many round trips to support a11y queries over bidi+

In case of puppeteer + mapper, this will be an internal call, without a roundtrip to the browser. But I'm not sure what is the specific scenario this is required to

When an A11y query is performed in Puppeteer, we get a backendNodeId. If the query is performed in a sandboxed realm, we need to DOM.resolveNode against the sandboxed realm instead of the default one.

[sadym-chromium]

LGTM, but please:

1. add an e2e test
2. update readme with this command

[sadym-chromium]

Thanks!