wpt.fyi
wpt.fyi copied to clipboard
web-platform-tests
web-platform-tests dashboard
When users click on `triage` button, there should be lint check that verifies the validity of triage metadata URLs and prompt users on the spot if they are invalid. Also...
This ability was dropped in the move from https://ecosystem-infra.github.io/wpt-results-analysis/compat to https://wpt.fyi/compat2021 , as the old tests list was not very usable anyway. We should try to lean on wpt.fyi's existing...
The default view currently shows two blink based browsers, one gecko browser and one webkit browser. This doesn't seem particularly helpful to anyone. For people trying to compare engines, having...
The accessibility check is removed from Travis due to https://github.com/web-platform-tests/wpt.fyi/issues/2450. It is fine because we won't ship major UI changes in the near term. In the long term, we should...
After the golang1.12 (and 1.14) upgrade, it is no longer possible to run the search cache locally. According to `api/query/cache/README.md`, this should be possible via: ``` cd api/query/cache/service go build...
Robert has left the team and the GitHub token needs to be updated. https://github.com/web-platform-tests/wpt.fyi/pull/2330
I wanted to link another bug today, which resulted in https://github.com/web-platform-tests/wpt-metadata/pull/217. https://bugs.webkit.org/show_bug.cgi?id=143842 is the bug I linked, at the end of the diff, but there are lots of other changes...
To reproduce: - Find a failing test and go to the individual test view, where youhave the test name and then a box for each browser with PASS/FAIL, "Compare" etc....
Repro steps: - Start at https://staging.wpt.fyi/results/?diff&filter=ADC&run_id=256970019&run_id=253050003 - Add `seq(status:ok status:!ok)` to search - Drill down to content-security-policy/inheritance/window.html You will be at https://staging.wpt.fyi/results/content-security-policy/inheritance/window.html?diff&filter=ADC&q=seq%28status%3Aok%20status%3A%21ok%29&run_id=256970019&run_id=253050003, showing this:  With only the harness status...
This is tricky to reproduce, but was discovered from the query listed in https://docs.google.com/document/d/1rLvhC1OjUizwLAm0rKoeqlA5wHcItn6F_vQHuA94HiA/edit?ts=600a2ecc : `((chrome:!missing&chrome:!pass&chrome:!ok) or (safari:!missing&safari:!pass&safari:!ok) or (firefox:!missing&firefox:!pass&firefox:!ok)) and none(triaged:chrome)` This query, plugged into wpt.fyi, initially caused a...