Turn on navigation to Interop 2025

[DanielRyanSmith]

Sets Interop 2025 as the default Interop year, and allows navigation to the 2025 dashboard.

[jcscottiii]

One question about the mobile_csv_url in the two files.

[jcscottiii]

I think you want the raw.githubusercontent.com URL for the mobile url. Also, there are no stable results for now. I only see experimental results for mobile.

https://github.com/jgraham/interop-results/tree/4cb9d304ea32acd6c2d35a86ed486b8b0f0a02e7/2025/latest/aligned

[DanielRyanSmith]

This is the URL used for the mobile results for 2024 as well, but we handle the mobile url differently to obtain the raw results view:

wpt.fyi/webapp/components/interop-data-manager.js

Lines 389 to 396 in 1723707

	if (isMobileScoresView) {
	const respJson = await csvResp.json();
	const csvText = atob(respJson['content']);
	csvLines = csvText.split('\r\n').filter(l => l);
	} else {
	const csvText = await csvResp.text();
	csvLines = csvText.split('\n').filter(l => l);
	}

There may be a better way of doing this, but this is what I found that worked 😅

Also, it is true that there are not stable results, but the link configuration is set up so that we can obtain stable results if they become available as scores.

[jcscottiii]

Actually given the fact we will get stable results sometime this year, ignore my initial concern. My follow up question: If someone selects stable, what will happen given that no stable results exist yet?

Also, thanks for the code. That helped. I ran it through a REPL with the current JSON payload and it makes sense.

[DanielRyanSmith]

We currently have 3 categories that display on the dashboard when the flag is set for mobile results.

So if we obtain stable mobile results sometime, this design will have to change to be more explicit and allow for viewing both sets of data.