Experimental Firefox Support

[kblok]

closes #1472
closes #1494
closes #1617

[slashP]

I'm not sure how far this work has come or if you want input, but when I try it out locally on Windows it fails with

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
   at PuppeteerSharp.States.ChromiumStartingState.<StartCoreAsync>d__6.MoveNext() in C:\dev\priv\puppeteer-sharp\lib\PuppeteerSharp\States\ChromiumStartingState.cs:line 82

after initializing with Product.Firefox in BrowserFetcherOptions and LaunchOptions. The error occurs first, then the browser does in fact start. Looking forward to seeing this working!

[kblok]

Hey @slashP what's the exception?

[slashP]

PuppeteerSharp.ProcessException: 'Failed to launch browser! on await p.StartCompletionSource.Task.ConfigureAwait(false); from the OnProcessExitedWhileStarting method it looks like. Process has start info:

StartInfo	FileName="C:\\blablabla\bin\\Debug\\net5.0\\.local-firefox\\Win64-87.0a1\\firefox\\firefox.exe", Arguments="--no-remote --foreground about:blank --remote-debugging-port=0 --profile \"C:\\Users\\blabla\\AppData\\Local\\Temp\\czwttcyf.iu3\"", WorkingDirectory=""

Not sure how to extract more info from it at this point.

[Androbin]

@kblok Why remove these?

[kblok]

It doesn't make much sense to test all the combinations with ENQUEUE_ASYNC_MESSAGES.
Puppeteer works well in .NET Core without enqueuing messages. That was implemented for .NET Framework users.