David, how important do you feel we need to run `w3c-css/received` in our reftest framework? From [this treeherder job](https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&resultStatus=superseded%2Ctestfailed%2Cbusted%2Cexception%2Csuccess%2Cretry%2Cusercancel%2Crunning%2Cpending%2Crunnable&revision=c65ef27b6fc78ec5140068913209bad3b55f1139&searchStr=web-platform) on m-c, we know have web-platform coverage on all platforms including Android. Considering the labor involved to update `w3c-css/received` reftests to the latest upstream wpt and update the test expectations (and keep it up to date), we could instead remove these tests as long as the pass/failure state is the same per bug 1490969 comment 66. What do you think?
Bug 1584324 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
David, how important do you feel we need to run `w3c-css/received` in our reftest framework? From [this treeherder job](https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&resultStatus=superseded%2Ctestfailed%2Cbusted%2Cexception%2Csuccess%2Cretry%2Cusercancel%2Crunning%2Cpending%2Crunnable&revision=c65ef27b6fc78ec5140068913209bad3b55f1139&searchStr=web-platform) on m-c, we now have web-platform coverage on all platforms including Android. Considering the labor involved to update `w3c-css/received` reftests to the latest upstream wpt and update the test expectations (and keep it up to date), we could instead remove these tests as long as the pass/failure state is the same per bug 1490969 comment 66. What do you think?