[meta] Tracking bug for web platform tests that only fail in Firefox
Categories
(Core :: General, enhancement, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox64 | --- | affected |
People
(Reporter: bzbarsky, Unassigned)
References
(Depends on 15 open bugs, )
Details
(Keywords: meta)
Updated•6 years ago
|
Updated•6 years ago
|
Comment 1•6 years ago
|
||
Comment 2•6 years ago
|
||
Comment 3•6 years ago
|
||
wpt.fyi now supports a structured-query syntax that supports searching by specific statuses, per-browser. Using this feature, a search for
!firefox:pass !firefox:ok (chrome:pass|chrome:ok) (edge:pass|edge:ok) (safari:pass|safari:ok)
will show "Firefox anomalies" / tests that only fail in firefox.
Comment 4•6 years ago
|
||
https://jgraham.github.io/wptdash/ can be used to get a list of tests that fail in Firefox but pass in Chrome & Safari, based on wpt.fyi data (url subject ot change, suggestions for improvement welcome).
Comment 5•6 years ago
|
||
lukebjerring, is the wpt.fyi URL in comment #3 correct? In many of the columns I see "N / N" for Firefox, which seems weird.
Are the exclamation marks just in the wrong place? The insights tab on staging.wpt.fyi suggests "(firefox:!pass&firefox:!ok) (chrome:pass|chrome:ok) (edge:pass|edge:ok) (safari:pass|safari:ok)" as the query, but I ran into this bug:
https://github.com/web-platform-tests/wpt.fyi/issues/1167
Updated•6 years ago
|
Updated•6 years ago
|
Comment 6•2 years ago
|
||
This meta bug isn't used anymore. Shall we close it?
Comment 7•2 years ago
|
||
Sure? Happy for anyone to reopen it if there's some use, but tracking per component might be easier.
Description
•