Interop 2024: Edge Canary or separate Chrome and Edge

[foolip]

Switching to Chrome Canary as suggested in #3579 has some knock-on effects on the presentation here:

Showing Chrome Canary + Edge Dev with a single score doesn't make sense as the score is often going to be different. In order to show "Edge Canary" we should actually have runs of Edge Canary.

Alternatively, we score Edge separately from Chrome. I think this has been suggested by @gsnedders but I can't find where now.

cc @dandclark

[dandclark]

My preference would be to move Edge to Canary as well.

[yisibl]

Will there be much difference in functionality between Chrome Canary and Edge Canary?

[gsnedders]

Alternatively, we score Edge separately from Chrome. I think this has been suggested by @gsnedders but I can't find where now.

web-platform-tests/interop#96

Will there be much difference in functionality between Chrome Canary and Edge Canary?

Using yesterday's aligned run, Chrome Dev has an overall interior score of 98.18%, whereas Edge Dev has an overall score of 95.62%.

I think this shows the differences.

That said, it might be interesting to know how much of that difference is caused by platform (an Edge run on Linux or a Chrome run on Windows would presumably show that!).

[past]

My preference would be to move Edge to Canary as well.

I support this as well, but I want to be clear that Chrome doesn't have the resources to work for this in 2023. We can only commit to getting results for Chrome Canary.

[foolip]

Here's a DevTools mockup of what this would look like if we switch to Chrome Canary and separate Chrome and Edge:

---

If Edge also switches to Canary:

[DanielRyanSmith]

This has been completed as of the Interop 2024 dashboard launch 🙂