In bug 64610, a new suite of tests were added. We need to triage them and land baselines. For now I'm going to mark them as PASS FAIL so the bots will go green. We should also wait until after bug 64567 lands to avoid unnecessary baseline churn.
Is it possible to make them reftests? We now switched to nrwt. It looks great opportunity to try it.
(In reply to comment #1) > Is it possible to make them reftests? > We now switched to nrwt. It looks great opportunity to try it. I support that. Looking at the failures, here are the issues: css3/selectors3/html/css3-modsel-d1.html css3/selectors3/html/css3-modsel-d1b.html css3/selectors3/html/css3-modsel-d2.html css3/selectors3/html/css3-modsel-d4.html css3/selectors3/xhtml/css3-modsel-d1.xml css3/selectors3/xhtml/css3-modsel-d1b.xml css3/selectors3/xhtml/css3-modsel-d2.xml css3/selectors3/xhtml/css3-modsel-d3.xml css3/selectors3/xhtml/css3-modsel-d4.xml css3/selectors3/xml/css3-modsel-d1.xml css3/selectors3/xml/css3-modsel-d1b.xml css3/selectors3/xml/css3-modsel-d2.xml css3/selectors3/xml/css3-modsel-d3.xml css3/selectors3/xml/css3-modsel-d4.xml Those tests are passing in the browser. They are failing as they don't have the required calls to testRunner.waitUntilDone / notifyDone. css3/selectors3/xhtml/css3-modsel-15c.xml css3/selector3/xml/css3-modsel-15c.xml Those are real failures. Wild guess, it looks like we don't implement selecting on xml:id and id at the same time. The rest of css3/selector3/xml/ failures are caused by bug 82122 along with some some flakiness in the output.
Marking test failures as WontFix. Bug is still accessible and recording in TestExpectations.