Maja Frydrychowicz

The protocol implementation in Firefox doesn't include `Fetch.enable` yet. The tracking bug is https://bugzilla.mozilla.org/show_bug.cgi?id=1587857 Similarly, the workaround you're trying depends on `Network.responseReceivedExtraInfo`, which also [not yet implemented in Firefox](https://bugzilla.mozilla.org/show_bug.cgi?id=1591937). Feel...

The problem encountered in the test is actually due to how the WPT harness constructs action sequences. See https://github.com/web-platform-tests/wpt/issues/25651

@domoritz Could you provide a trace-level log for this script to help us investigate? (https://searchfox.org/mozilla-central/source/testing/geckodriver/doc/TraceLogs.md)

Excellent, thanks. @domoritz Does this also happen with `driver.execute_script`?

See workaround at https://github.com/puppeteer/puppeteer/issues/5743#issuecomment-621664876 On Fri., Jul. 17, 2020, 02:54 Mathias Bynens, wrote: > Once puppeteer-firefox is no longer experimental, npm i puppeteer will > install both browsers. > >...

@LarsDenBakker What would your short-term solution be?