1623297 - Runtime.callFunctionOn doesn't return objectId when returnByValue is false

Status: RESOLVED WONTFIX

(Remote Protocol :: CDP, defect, P3)

Description

[Henrik Skupin [:whimboo][⌚️UTC+1]]

The following can be replicated in a Puppeteer test when using the following line:

let element = await page.waitForSelector("h1");

Here how Chrome behaves:

 puppeteer:protocol SEND ► {"sessionId":"FFF0703460B692B2245C6733A21F3608","method":"Runtime.callFunctionOn","params":{"functionDeclaration":"async function waitForPredicatePageFunction(predicateBody, polling, timeout, ...args) {\n  const p
[..]
"value":"h1"},{"value":false},{"value":false},{"value":false}],"returnByValue":false,"awaitPromise":true,"userGesture":true},"id":18} +3ms
  puppeteer:protocol ◀ RECV {"id":18,"result":{"result":{"type":"object","subtype":"node","className":"HTMLHeadingElement","description":"h1","objectId":"{\"injectedScriptId\":4,\"id\":1}"}},"sessionId":"FFF0703460B692B2245C6733A21F3608"} +4ms

And that is what we currently get with Firefox:

  puppeteer:protocol ◀ RECV {"sessionId":1,"id":18,"result":{"result":{"type":"object","subtype":"node"}}} +8ms

The objectId is needed for commands like describeNode, and not returning it will break certain parts of element interaction.

Comment 1

[Firefox Bug Husbandry Bot]

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)

Comment 2

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Remote value serialization and deserialization works fine with WebDriver BiDi. As such we won't fix this bug.