7 replies

1. Kirch 10 min later

   @zachleat feels more like management knows less about The Web, in general, let alone what's on their own website, than ever before...

2. haliphax 👾 18 min later

   @zachleat Which is a real shame, because in my long term experience developing for the web, it's only gotten easier. Modern tooling (e.g. vue test utils, happydom) has grown to be pretty capable, and integration (e.g. cypress, playwright) is better than ever.

3. ahoyboyhoy 58 min later

   @zachleat by feature testing, do you mean "does this environment support feature x?", as in early days of HTML5 where SVG as image src, media tags, and a great many other features were not reliably available in a browser (and would require polyfill)?

   1. Zach Leatherman 1 hr later

      @ahoyboyhoy yeah, writing JavaScript to test for features, a la Modernizr: https://modernizr.com/

4. westbrook 2 hr later

   @zachleat The jump to APIs not being prepared for this sort of testing seemed to go by the wayside with the `type="module"`/`no-module` toggle. There was a glimmer of a hope we'd be given some form of successor to this...but, no.

   1. Zach Leatherman 4 hr later

      @westbrook https://developer.mozilla.org/en-US/docs/Web/API/HTMLScriptElement/supports_static#speculationrules seems like at least someone is thinking about it!

      1. westbrook 5 hr later

         @zachleat So close to being able to say `HTMLScriptElement.supports('css import attributes')`... 🥺