wpt.fyi
wpt.fyi copied to clipboard
web-platform-tests
web-platform-tests dashboard
A timeline error was brought to our attention: > Hi, question about WPT. This test is failing in Chrome according to that website: https://wpt.fyi/results/css/css-contain/content-visibility/content-visibility-with-top-layer-005.html?label=master&label=experimental&product=chrome&product=firefox&product=safari&aligned&view=interop&q=label%3Ainterop-2022-contain%20or%20label%3Ainterop-2023-contain But if you click "show history...
It would be nice to see the date and time (and maybe also the commit SHA) of the last aligned test run the interop page(s) is/are based on. Why? You...
There is a lot of important information about the Interop effort and the dashboard that is not explicitly documented here. It could be useful to move some of the major...
I was trying to search for `shadow-dom/DocumentOrShadowRoot-prototype-elementFromPoint.html or shadow-dom/MouseEvent-prototype-offsetX-offsetY.html`, however in both STP 156 and Chrome 109 this gets lowercased and finds nothing. Oddly, copying the URL gives me the...
Fixes #3009. I'm not sure why the test fails, as far as I can tell from https://polymer-library.polymer-project.org/3.0/docs/devguide/data-system setting `queryInput` should be running the `queryInputChanged` observer, which should call `latchQuery` after...
For example, https://wpt.fyi/analyzer?screenshot=sha1%3A3945da270ca8ccb106ba327ee1a3a1793934dc71&screenshot=sha1%3A5c3df965b7d8fdbfc3a07181f464cd57ad26391c The results are for css/css-pseudo/active-selection-018.html but that test name does not appear anywhere in the URL or on the comparison page. When filing bugs against test faulures,...
Given a number of different search queries on wpt.fyi, you might think you could merge them with something like: ```js const merged = queries.map((q) => `exists(${q})`).join(" or "); ``` However,...
e.g. `(path:/css/css-display and exists(display contents))`, https://wpt.fyi/results/?label=master&label=experimental&aligned&q=%28path%3A%2Fcss%2Fcss-display%20and%20exists%28display%20contents%29%29 This leads to a request to https://wpt.fyi/api/search which returns 400 ("Failed to parse query fragment as any of the existing search atoms in wpt.fyi/api/query/README.md")....
This is restating https://github.com/web-platform-tests/interop/issues/370. In order to show results faster, we should score all runs for each browser, not just aligned runs. Interop scores will still need to use aligned...
This to track https://github.com/web-platform-tests/interop/issues/356 along with the other requests for the Interop 2024 dashboard.