[Bug]: Issue with BiDi-powered logging

[mathiasbynens]

Bug expectation

I expected to get a message logged to my terminal, but I didn’t get any.

Bug behavior

• Flaky
• PDF

Minimal, reproducible example

import puppeteer from 'puppeteer';

const browser = await puppeteer.launch({
  protocol: 'webDriverBiDi',
});

const context = await browser.createIncognitoBrowserContext();
const page = await context.newPage();

page.on('console', (message) => {
  console.log(`Unexpected console message received: [${
    message.type()
  }] ${message.text()}`);
});


await page.goto(`data:text/html,<script>console.log('1');</script>`);

Error string

No error

Puppeteer configuration

No response

Puppeteer version

19.9.0

Node version

16.14.0

Package manager

npm

Package manager version

8.14.0

Operating system

macOS

[sadym-chromium]

I added the following script to the file example/qwe.js of Puppeteer and run it via NODE_PATH=../ node examples/qwe.js. I get the Unexpected console message received: [log] 1 message in console. What did I do wrong?

const puppeteer = require('puppeteer');

(async () => {

  const browser = await puppeteer.launch({
    protocol: 'webDriverBiDi',
  });

  const context = await browser.createIncognitoBrowserContext();
  const page = await context.newPage();

  page.on('console', (message) => {
    console.log(`Unexpected console message received: [${
      message.type()
    }] ${message.text()}`);
  });

  await page.goto(`data:text/html,<script>console.log('1');</script>`);
})();

[sadym-chromium]

First suspect is not waiting for the subscribe command to finish:

puppeteer/packages/puppeteer-core/src/common/bidi/Page.ts

Line 53 in 57c5727

this.#context.connection

[sadym-chromium]

The root cause is fixed in Mapper in GoogleChromeLabs/chromium-bidi@55680d5. Puppeteer needs to be updated.

[Lightning00Blade]

Closed by #10060