Randolf J.

Just to confirm, you're saying cookies from headful/normal mode are being read from headless/incognito mode, right?

> Headful and headless runs are independent from each other, cookies are not shared between these runs. I understand this, but I'm trying to understand your claim. Is your claim...

@OrKoN This issue should be independent of --user-data-dir since incognito mode is explicitly specified.

We are not able to reproduce with our own SSO. Please add a full MVCE for us to continue. Otherwise, we will not be able to help.

If you use `domcontentloaded` instead of `load`, the above script will work, however this is a Puppeteer bug. The underlying problem here is that the `reload` and `goto` wait on...

> I am not sure that would work as we also have networkidle events on the list of supported event that might take a long time to occur (possibly infinitely)...

In CDP it shows that `domcontentloaded` happens after `load`. In particular, what happens (if you remove `page.reload`) is the `load` happens, then the query, then the `domcontentloaded`. From looking at...

A functional repro: ```ts import * as Puppeteer from "puppeteer"; const browser = await Puppeteer.launch({ ignoreHTTPSErrors: true, headless: false, devtools: true, }); const page = await browser.newPage(); await page.goto("https://ilsole24ore.com", {...

Looks to me like the proxy is problematic. Have you verified that you can navigate to ip.me through the proxy? (Without using Chrome or Puppeteer)

The comment applies only when you use the key code for the key down. For example, ```ts const puppeteer = require('puppeteer'); (async () => { const browser = await puppeteer.launch();...