Nikolay Vitkov

Results 130 comments of Nikolay Vitkov

@SK-FComputer Can you try to run your code with version `21.4.1` and use `PUPPETEER_EXECUTABLE_PATH` env or `executablePath` property of the `launch` command - pointing to the old binary installed by...

Moving to draft will revisit, before submitting.

``` @Lightning00Blade is it expected to pass for the Chrome version in wpt.fyi? ```` @OrKoN Sadly it will fail via ChromeDriver as we run `chromium-bidi` in a tab and it's...

@ruelustin5 Hello you can read about the differences [here](https://developer.chrome.com/docs/chromium/new-headless). Can you try using `headless: "new"` ? That should have the same behavior as `headless: false`.

@sadym-chromium I am not sure if this will be picked up correctly by release-please, so please use `feat!`,`fix!` or `refactor!`

Testing again with 125.0.6422.14 seems to work so waiting till that or newer version rolls to stable to re test. https://gist.github.com/Lightning00Blade/338850f93f6379a60a414aaa3ea6ed99

There is already a bug on Chromium to add support for this option: https://issues.chromium.org/issues/41387522#comment48 Please upvote that feature request as it signals interest in the feature.

The `puppeteer.connect` are not cleared property and leave some things open. I am working on a fix for that. While investigating I found another bug: In the test `should reject...

@pfeileon Could you elaborate on the last point > It's impossible to run ng e2e in a CI environment without also pointlessly starting the dev-server. What's your use case and...

I have tracked down the issue and it's that there is a bug in Chromium where there is no interception for an update from insecure to secure (header: `"Upgrade-Insecure-Requests":"1"`), and...