Infer reproducibility through browser logs

[GJFR]

Ideally, we would be able to infer the reproducibility of a bug, not only through sent requests, but also through browser logs.
This way, console.log() calls would be logged to a file that is readable by the worker container in which the browser runs.

However, this doesn't seem to be straightforward to implement, nor robust for all experiment scenarios.
For example, Chrome (and Firefox?) will not log console output when in incognito mode.

Current status (not implemented):

• Chrome: logging works quite well if in --headless mode, up until +/- version 110. Using the new --headless=new for versions after 110 also doesn't seem to be robust (e.g., browser crashes or doesn't start properly).
• Firefox: I still haven't figured out how to include console output in browser logs.

For now, this idea will be put into the freezer. However, it would be convenient to have another way of inferring reproducibility, other than requests / traffic.

[GJFR]

This should be a priority, based on discussions at Black Hat USA 2024.

Possible alternative: detection of alert()?