jgraham

I mean one could have something like `maxDifference=0-50;totalPixels=0-400;condition='product == "firefox" and os == "win" and debug'` but architecturally getting access to the condition parsing and evaluation code inside wptrunner would...

In terms of actually allowing subtests of reftests, I can imagine two possible ways to do that: 1) Consider each variant (identified by a unique query string or fragment, and...

I think this still makes sense, but should be done as a followup to https://github.com/web-platform-tests/rfcs/pull/98 as e.g.`RemoteWindow.testdriver.click` and similar.

My view is that if people want to use the concept of browser specific failures as an internal tool for understanding areas of interop difficulty that's good, and I fully...

I think a proposal for a new interop metric, even if based on BSF, would clearly be something for the Interop team to consider.

Whilst I'm happy that Chrome's leadership are finding the graph useful, that usefulness as a metric is not a consensus position among browser vendors, and therefore it seems more appropriate...

So we can't use auto-formatting because we can't enforce that all downstream consumers (Blink, Gecko, etc.) have exactly the same versions of the same tools installed. We especially don't want...

> We could also do likewise with the merge tags. That would be a ~breaking change for the gecko sync (we use the tags in the first instance to associate...

> My motivation is to make git fetch and git log less noisy. Can you update the RFC with this reasoning?

Some more details about what Gecko/Firefox does for Android testing: We're running wpt in CI in the Android emulator. wptrunner runs on the host machine, and the frontend launches the...