How to use ShouldWorkWithConditionals method of PuppeteerSharp.Tests.CoverageTests.JSCoverageTests class

Not sure you can disable the built in download manager with --disable-extensions.

Another approach if it is just ZIP's you want to stop is to plumb this code in:-

await page.setRequestInterception(true);
page.on('request', request => {
    if (request.url().endsWith('.zip'))
        request.abort();
    else
      request.continue();
});

You may also want to lower case the url so you also trap .ZIP abnd Zip etc

Also on your goto you will need to abort the request e.g.

  await page
        .goto("https://winaero.com/downloads/Win7Games4Win10_8_81_v2.zip")
        .catch(r => r.abort);

I would use WaitForSelectorAsync instead:

var frameElement = await page.WaitForSelectorAsync("#google_ads_frame5");
var frame = await frameElement.ContentFrameAsync();
var frameContent = await frame.GetContentAsync();

From the examples in the docs, it looks like you have to do this:

// select the tag first
var element = await _page.QuerySelectorAsync("h1 > strong > a");

// then get the attribute
var url = await element.EvaluateFunctionAsync<string>("e => e.getAttribute('href')");
// OR
var url = await _page.EvaluateFunctionAsync<string>("e => e.getAttribute('href')", element);
// OR
var url = await (await element.GetPropertyAsync("href")).JsonValueAsync<string>();

// OR all in one
var url = await _page.EvaluateExpressionAsync<string>($"document.querySelector({"'h1 > strong > a'"}).getAttribute('href')");

You gotta apply this to the value of a select option, of course. Probably 'value' instead of 'href' and the correct selector.

You can close the page using CloseAsync:

var page = browser.NewPageAsync();
////
await page.CloseAsync();

An using block will also close the page:

using (var page = await new browser.PageAsync())
{
///
}

Puppeteer-Sharp v2.0.3+ also supports await using blocks

await using (var page = await new browser.PageAsync())
{
 ///
}

You have to be careful with your domain property. If it's not valid, it will be ignored. For what I see there. You might be setting something like http://www.yourdomain.com, when yourdomain.com is expected.

You can use the PdfOptions.Height and PdfOptions.Width.You might find that it's not pixel perfect but that's more on the Chromium's side than on Puppeteer's.

await page.SetViewportAsync(new ViewPortOptions()
{
    Height = 1024,
    Width = 1280
});
await page.GoToAsync("https://github.com/kblok/puppeteer-sharp/");
int height = await page.EvaluateExpressionAsync<int>("document.body.offsetHeight");
int width = await page.EvaluateExpressionAsync<int>("document.body.offsetWidth");
await page.PdfAsync(Path.Combine(Directory.GetCurrentDirectory(), "test.pdf"), new PdfOptions
{
    Width = width.ToString() + "px",
    Height = height.ToString() + "px",
});

You can close the page using CloseAsync:

var page = browser.NewPageAsync();
////
await page.CloseAsync();

An using block will also close the page:

using (var page = await new browser.PageAsync())
{
///
}

Puppeteer-Sharp v2.0.3+ also supports await using blocks

await using (var page = await new browser.PageAsync())
{
 ///
}

After struggling with the issue for several hours, we finally located the issue. It is not related with Puppeteer that works like a charm but rather with the way a private blob storage container handles authentication: as our request contained an Authorization HTTP Header with a bearer token required by our own app, this header was sent by Chromium while retrieving remote images from the blob container. Unfortunately Azure service tried to handle that token and rejected our request.

How did we identify that? By connecting a chrome debugger to the Chromium instance and by checking the logs. Indeed it is possible to launch Puppeteer with a remote debugging port.

You can wait for some selector that might tell you that the page is ready. e.g.:

await page.WaitForSelectorAsync(".someSelector");