10 replies

1. Stuart Robson 8 min later

   renaming this side project to "Can I Baseline?"

   1. Zach Leatherman 22 min later

      I’M INTERESTED

2. Patrick Brosset 25 min later

   We're definitely interested in talking more about this on the WebDX CG. Progressive enhancements, polyfills, and accessibility have come up multiple times in the past. So far, we've not been able to incorporate these aspects into Baseline calculation though. But I do believe we should.

   1. Patrick Brosset 30 min later

      One of the things I've tried to steer the group towards in the first years of the project is to avoid "hiding" things that are not yet supported. Anything we can do to make features easier to discover/use, not harder, is valuable.

      1. Zach Leatherman 54 min later

         interesting! “hiding” in what view?

         1. Patrick Brosset 56 min later

            As in, Baseline comes with the risk of hiding too many features from the web: those that aren't supported across browsers even though they're perfectly fine to use.
            Showing a "Limited" Baseline banner on a doc website about a given feature comes with the risk of steering people away from it.

            1. Zach Leatherman 1 hr later

               Ah, I see — yeah. That dovetails back to Baseline missing some pieces if you want to encourage or discourage usage on a feature, imo! “Limited but safe!”

               1. Patrick Brosset 1 hr later

                  Filed github.com/web-platform... to put it on our radar. We'll likely discuss at our next CG meeting (which you're more than welcome to join, details here: www.w3.org/community/we...), but please feel free to comment on the issue too.
                  Pinging @miriam.codes who had made a similar point too.

                  1. Zach Leatherman 2 hr later

                     appreciate you Patrick! 🙌

3. Zach Leatherman 1 day later

   Some additional discussion is happening on this GitHub Issue: github.com/web-platform...

   Thanks @patrickbrosset.com for filing!