How to use ValueFromType method of PuppeteerSharp.Helpers.RemoteObjectHelper class

I think you should not do a .ConfigureAwait on the controller level, look at this article for more information: https://blog.stephencleary.com/2017/03/aspnetcore-synchronization-context.html.

ASP.NET team dropped the use of SynchronizationContext, so using it in your controller is pointless.

As the article states, you should still use it on your service level, as you don't know whether or not a UI could plug itself to the service and use it, but on your WEB API, you can drop it.

Based on Line 43 of the LanchOptions.cs you can specify arguments to the launch process.

Now connecting this with the native JavaScript (using the --load-extension flag) the output should look similar to the following:

var browser = await Puppeteer.LaunchAsync(new LaunchOptions
{
    Args = new string[1] { "--load-extension=/Path/To/Extension/Folder" }
});

Note: that I put path to folder, not the .zip as you have in your sample.. if you want to load multiple extensions then just separate the paths using a comma.

Here's a full list of possible arguments that can be passed in to Chromium.

using below,

using var page = browser.NewPageAsync().Result;

page.TypeAsync("input[name='elementname']", valuetobeset).Wait();

You can call EvaluateFunction passing that ElementHandle as an argument

var content = await Page.EvaluateFunctionAsync<string>("e => e.textContent", elementHandle);

If you have many scenarios like that, you can build an extension method to solve that for you ;)

The execution of the GetCookiesAsync task needs to be awaited, like this:

private async Task YourMethod()
{ 
    var result = await page.GetCookiesAsync();
}

You might need to change your callers for this.

Try to read about asynchronous programming in C#: https://learn.microsoft.com/en-us/dotnet/csharp/programming-guide/concepts/async/

So what you are seeing with this:

Id = 7315, Status = WaitingForActivation, Method = "{null}", Result = "{Not yet computed}"

is the async task not yet completed. GetCookiesAsync returns immediately. If you want to want to wait for the result, you should await it.

You shouldn't turn those flags on unless you get stuck :)

• EnqueueAsyncMessages was created for cases where your code is not async all the way. I honestly dislike that flag.
• EnqueueTransportMessages is recommended on .NET Framework code because the websocket library behaves differently there.

Regarding ResourceTypes, ResourceType.Image comes from Chrome and ResourceType.Img comes from Firefox.

You can do something like this:

await page.EvaluateExpressionAsync("document.querySelectorAll('SCRIPT').forEach(e => e.remove())");

First thing, you need to launch Chrome with remote debugging enabled. If you launch Chrome, for instance, with the flag --remote-debugging-port=2122, you know that you will be able to connect to the browser using the http://127.0.0.1:2122 URL.

Second, if you want to connect to an existing browser you need to call ConnectAsync instead of LaunchAsync.

Having all that. If would be a matter of doing something like this:

var browser = await Puppeteer.ConnectAsync(new ConnectOptions
{
    BrowserURL = "http://127.0.0.1:2122"
}));

Either give your submit button an id property and use the #submit selector you previously tried:

<button id="submit" type="submit" class="btn btn-danger btn-lg btn-block">Login</button>

Or use form button[type=submit] as selector.