Closed SuperSonicHub1 closed 2 years ago
After doing further investigation it seems that specifying --headless
causes a different binary to be opened which indeed doesn't have --enable-webrtc
as a command line flag. I guess I now need to open up a WebKit bug?
I'm going to be closing this issue as it's likely out of scope for you all. I think it would be good to clarify here that there is significantly different behavior for how WebKit works depending on if headless
is set to false
or true
.
Context:
Code Snippet
Help us help you! Put down a short code snippet that illustrates your bug and that we can run and debug locally. For example:
Describe the bug Running
~/.cache/ms-playwright/webkit-1683/pw_run.sh --enable-webrtc=0
runs MiniBrowser just fine and no command line parsing issues come up. However, when I replicate the same command with Node or Python, I get this error:--enable-webrtc 0
also works on the command line, but then Playwright thinks you're trying to specify a webpage URL: