Alex Rudenko
Alex Rudenko
The issue can only be solved by the Chromium team: please report it at crbug.com if it persists in the latest version.
Closing as we were not able to reproduce it at this time, perhaps it is some limitation on the reporter's system that leads to timeouts.
Closing as there is no good way to test this. Please file a new issue if there is a reproducible example.
Note enough information to reproduce: which requests are missing? DevTools shows many requests that might not come from the page. Also, please retry using the latest Puppeteer version as there...
@sidvishnoi I don't think there is an upstream bug. I am not quite sure it's an upstream bug at this point: perhaps the Network.requestWillBeSent is dispatched on the worker target...
It appears that either something in Puppeteer fixed it or more likely upstream changes. I am not able to reproduce it with 22.6.3
The demo says the canvas needs to be clicked first. ``` const puppeteer = require('puppeteer'); (async() => { const browser = await puppeteer.launch({ headless: false }); const page = await...
Could you please rebase if you want to land this? I will close it for now as the PR looks fairly minor and you would not want to rebase it...
I was looking into the bug but unfortunately I was not able to get to the bottom of it. I wonder if it started to working with the latest Chrome...
Please try using the latest version if it is still relevant.