10 replies

1. siggiarni Mastodon 2 min later

   @zachleat Ís-land? 🇮🇸

   1. Zach Leatherman Mastodon 4 min later

      @siggiarni 💯💯💯💯

2. rem Mastodon 2 hr later

   @zachleat question, that I don't think quit think warrants a github issue/qusetion: why use the `on:x` attribute pattern over something like `data-on-condition`? Just curious.

   1. Zach Leatherman Mastodon 2 hr later

      @rem I don’t believe `data-` is required for custom elements so just a style preference

      1. Dan Ryan Mastodon 6 hr later

         @zachleat @rem that’s also my understanding. HTML spec will never ship a tag name with a hyphen, so there will never be a clash with an attribute _unless_ you use one that HTMLElement has like “name” or “role”.

         1. Zach Leatherman Mastodon 6 hr later

            @d @rem although certain conflicts *could* arise if new attributes are added—hmm. Thinking I might need to test how conflicts work

            1. Dan Ryan Mastodon 6 hr later

               @zachleat @rem agreed. I think custom namespaces may still be best. And data- is certainly fine to use.

3. Marc Khoury Mastodon 7 hr later

   @zachleat Can I untap it during my untap phase?

   1. Zach Leatherman Mastodon 1 day later

      @mkhoury web components: the gathering!

      1. Marc Khoury Mastodon 1 day later

         @zachleat that actually might be a good organizing model. Each web component library is like a color; a component plays well with all other libraries, but it does it particularly well within the library.