Philip Jägenstedt

That's cool :) Note that if you ever want to run a single test and don't want the window to stay open you can use `--no-pause`.

@beaufortfrancois once https://github.com/web-platform-tests/wpt/pull/13769 has landed, you should be able to submit a PR that tweaks .azure-pipelines.yml a bit to run the test using Safari Technology Preview, for a second data...

@beaufortfrancois if you're getting `unrecognized option `--version'` then you're probably not using the most recent Safari Technology Preview. Does `/Applications/Safari Technology Preview.app/Contents/MacOS/safaridriver --version` also give you that error? If so...

Sorry, there were two `./wpt run` invocations in your code block, and only the second one shows the warning. That's as expected until the next Safari stable release.

@beaufortfrancois is there anything in https://github.com/WebKit/webkit/blob/master/Source/WebCore/html/HTMLMediaElement.cpp that provides hints? Without reading code, my guess would be that the window isn't considered focused or visible when run under automation, and that...

@jugglinmike have you looked at running Chrome headless? I think there is an argument for exercising the headless codepaths, namely that this is what web developers setting up cross-browser testing...

@andreastt the searchfox.org link you shared doesn't seem to list test statuses, should I be able to see a list of tests that do differ between headless and Xvfb there?

I've filed https://github.com/web-platform-tests/wpt/issues/13005 for the CLI feature request.

Oh, wow, that's not quite ready to land then :) I'm afraid I don't have any tips, if we wanted to pursue this we'd have to dig into the failure...

I'm OK with this. There is still a small problem with the mojo files and code to create the testing APIs being checked into WPT, since actually they evolve together...