8 replies

1. Nathan Knowler 4 min later

   @zachleat Just wait until you see `customElements.define()`. Baseline is showing some potential to a setback for Web Component adoption.

   1. Zach Leatherman 16 min later

      @knowler OH NO, what!

   2. McNeely 2 hr later

      @knowler @zachleat Ok Baseline Safari isn't *that* far behind providing support jeez....

2. Zach Leatherman 17 min later

   As @knowler notes, this is also a problem with `customElements.define()` too! 😭

   https://developer.mozilla.org/en-US/docs/Web/API/CustomElementRegistry/define

   1. Zach Leatherman 4 hr later

      The official issue for these can be found at https://github.com/web-platform-dx/web-features/issues/562

      HT @McNeely @darth_mall@notacult.social @elomatreb

3. elomatreb 🚂 24 min later

   @zachleat https://github.com/web-platform-dx/web-features/issues/562 looks relevant

4. Vadim Makeev 1 hr later

   @zachleat The feedback form works fine for all kinds of issues with this widget. Feel free to use it! In this case, two sources of data (BCD for the table and web-features for the banner) are correct. But the way they’re represented on the banner is misleading. We at MDN know this issue and are working on fixing it.

   1. Zach Leatherman 1 hr later

      @pepelsbey Ah, great! Thanks for fielding my toot 🫣

      I was very surprised to learn that Baseline reports compatibility data from an arbitrary aggregate grouping of features—that seems to be a much larger problem!