[Bug]: `DOM.requestNode` returns `nodeId=0`

Bug description

Steps to reproduce the problem:

1. Visit a page with an element with id=demo_id and open a CDP session
2. Obtain the RemoteObjectId of the node, using Runtime.evaluate with {expression:"demo_id"}
3. Request the corresponding NodeId using DOM.requestNode
4. Issue: Get back nodeId=0…? To compare: execute the following in the experimental Protocol Monitor console in the Chromium devtools:
5. {"command":"Runtime.evaluate", "parameters":{"expression":"demo_id"}}
6. {"command":"DOM.requestNode", "parameters":{"objectId":"<RemoteObjectId just obtained>"}}
7. Get back the actual nonzero NodeId (If you execute this in the same browser as the previous steps, you will notice that that the RemoteObjectId obtained in step 5 is the same as in step 2. However, if you execute step 6 without executing step 5 you will get back Could not find object with given id. Not sure if this is by CDP design?)

This may well be an upstream issue, but I’m not sure what causes it to work fine in the devtools and not via Puppeteer.

Script:

import puppeteer from 'puppeteer';

const browser = await puppeteer.launch({headless: false});
const page    = await browser.newPage();
await page.goto('data:text/html,' + encodeURIComponent('<input id=demo_id />'));

const cdp = await page.target().createCDPSession();
await cdp.send('Runtime.enable');
await cdp.send('DOM.enable');
const {result: {objectId}} = await cdp.send('Runtime.evaluate', {expression: 'demo_id'});
console.log(objectId);  // Correct id
const {nodeId} = await cdp.send('DOM.requestNode', {objectId});
console.log(nodeId);  // 0 ??

Puppeteer version

18.2.1

Node.js version

18.9.0

npm version

8.19.2

What operating system are you seeing the problem on?

Windows

Relevant log output

3462418028677997700.3.1
0

[stevenwdv]

(Chromium bug is now at https://crbug.com/1374241. Your workaround using DOM.getDocument seems to work, even with depth=0)

[stevenwdv]

@OrKoN Ok thanks, that might be the cause, I guess I’ll report it there then. I need the NodeId for DOMDebugger.setDOMBreakpoint btw.