Bug: [Headful mode] FrameManager throws exceptions when user navigates quickly

[yellowduckling]

When using PuppeteerSharp in headful mode, the library sometimes throws exceptions internally in FrameManager and related classes (IsolatedWorld, Client_MessageReceived) if the user manually navigates tabs or rapidly changes URLs (e.g., via keyboard shortcuts).

This occurs even if the user code does not trigger any navigation or frame evaluation. The exceptions appear in places like:

await OnFrameNavigatedAsync(response.Frame, response.Type).ConfigureAwait(false);
_logger = Client.Connection.LoggerFactory.CreateLogger();

Steps to reproduce:

1. Launch a browser in headful mode:
2. Open a page.
3. While the page is loaded, manually switch tabs or rapidly change the URL using browser shortcuts.
4. Observe that PuppeteerSharp throws exceptions internally (e.g., PuppeteerException) even though no user code is calling EvaluateAsync or GoToAsync.

Observed behavior:

Exceptions occur inside internal event handlers, like Client_MessageReceived and IsolatedWorld constructor.

[kblok]

I don't know whether putting an automation tool to interact with a real user is a good idea.

[yellowduckling]

Yeah, I totally get what you mean.

That said, the issue here isn’t really about trying to automate while a user interacts. It’s more about the fact that when running in headful mode, PuppeteerSharp can throw unhandled exceptions internally just because the user does something simple like switching tabs or changing the URL.

Even if my code isn’t doing anything at that moment, the library’s internal event handlers (FrameManager, IsolatedWorld, etc.) still blow up because of out-of-order frame events.

Ideally, PuppeteerSharp would just handle those cases gracefully ignore the bad events or log a warning instead of throwing and killing the connection. That would make it a lot more stable for apps that use Chrome for visualization, monitoring, or partial automation, not just full automation.

So yeah, I get that this isn’t the main use case, but handling it safely would make PuppeteerSharp more robust overall.