Open gsnedders opened 6 years ago
Per spec, FWIW:
compositing: 1 css-color: 1 css-images: 1 css-transforms: 1 selectors: 1 vendor-imports: 1 css-values: 2 css-animations: 4 css-text-decor: 4 css-transitions: 6 css-flexbox: 8 css-display: 11 css-page: 14 css-fonts: 18 css-gcpm: 19 css-backgrounds: 22 css-counter-styles: 24 css-regions: 31 css-writing-modes: 36 css-ui: 165 CSS2: 517
css/vendor-imports/mozilla/mozilla-central-reftests/text3/text-align-match-parent-01.html
is fixed in https://bugzilla.mozilla.org/show_bug.cgi?id=1427114
https://bugzilla.mozilla.org/show_bug.cgi?id=605520 is another potential source of failing CSS2 tests (though whether they pass in other browsers is another question!).
@gsnedders what engine builds did you test against for the above table?
@gregwhitworth It's simply done by counting results the CSS Test Harness has, and taking the majority result, all with no regard for browser versions. It's far from perfect, but the CSS Test Harness doesn't have results for the latest version of most browsers for most tests (heck, see all the tests with no Edge result).
The following table is derived from data from the CSS Test Harness, showing tests that are visual or manual tests and pass in at least one browser and fail in at least one. These are, therefore, the visual/manual CSS tests that are probably the highest priority to automate given they reveal interoperability issues.
Here's a to-do list for tracking. It's known that not all of these can be automated currently; for those that can't be, they can be marked done when there's an issue for the reason they can't be automated and they should be annotated with that issue.
Tests done prior to regrouping
Visual tests
Tests flagged with: userstyle
Tests flagged with: paged
Tests flagged with: animated
Tests flagged with: interact, animated
Tests flagged with: interact
Tests flagged with: font
Tests flagged with: interact, paged
Tests flagged with: interact, history