jgraham

https://www.ekioh.com/ have the Flow engine, which is mainly focused on embedded use cases.

Well there are already more than just `disabled`, `bug` and `expected`, so I'm not sure I want to make a whitelist that has to be updated for any new feature...

We got the feedback internally that Phase 2 is too early for WASM. For something to be in Interop we'd expect it to be reaching Phase 4 by the end...

Working backwards, I'd expect that _after_ Interop a proposal would be in at least Phase 4 i.e. multiple implementations would pass the testsuite. Therefore that doesn't make sense as an...

Note that this isn't quite true, we ended up with a one-off port of the backreference tests. If we want to accept features that are only tested in test262 going...

We do have enough data in the CI to tell that a) a test is an Interop test and b) that results got worse in some browsers. Therefore a policy-we-could-enforce-in-code...

> For keeping historical results unchanged, an alternative way to achieve that is to move labels into WPT itself somehow, in a way where it's possible to get the labels...

Right, the proposal is not to display the graphs of historic scores by default, but to have an option to display them instead of the current graph, so that in...

So, the previous situation was that each variant is its own top-level test for the purposes of scoring, and the proposal is that we define things based on the file...

Our priorities for the dashboard in 2024 are: * Support for seeing actual historical scores without rescoring (so there's always some way to see that yes, at the displayed score...