[wpt] Allowing *.any.js tests in CSS folders.

[emilio]

Right now if you want to add a *.any.js test to WPT (to, e.g., test TypedOM interfaces in workers) you can't, because of this lint rule:

class MissingLink(Rule):
    name = "MISSING-LINK"
    description = "Testcase file must have a link to a spec"
    to_fix = """
        Ensure that there is a `<link rel="help" href="[url]">` for the spec.
        `MISSING-LINK` is designed to ensure that the CSS build tool can find
        the tests. Note that the CSS build system is primarily used by
        [test.csswg.org/](http://test.csswg.org/), which doesn't use
        `wptserve`, so `*.any.js` and similar tests won't work there; stick
        with the `.html` equivalent.
    """

My understanding is that test.csswg.org is no longer a thing, so can we lift that restriction? To be clear I still think it's useful for html tests to have a <link rel=help> but it makes testing workers a lot harder.

Filing an issue here just in case I'm missing something?

cc @janvarga @astearns @tabatkins @fantasai

[svgeesus]

My understanding is that test.csswg.org is no longer a thing, so can we lift that restriction?

Yes, that has not been a thing for many years; it was totally unmaintained, required manual testing, and was replaced by wpt ages ago.

[svgeesus]

To be clear I still think it's useful for html tests to have a <link rel=help>

Yes, absolutely! It is not just for the old build tool. It is also useful for specification authors to rapidly understand what a test is claiming to be testing.

[emilio]

Ok, so probably that lint rule should only apply to html tests. That seems like the lowest friction change. I don't know if we can lint for that kind of metadata in js tests.

[Ms2ger]

Jan added support for spec metadata in web-platform-tests/wpt#60969; can this be closed?

[emilio]

Yes.