The more I dig down the various rabbit holes in Google’s new Web Platform Dashboard, the less I understand it. I think I need an explainer that’s more detailed than the launch blog post. Anyone have a lead on such a thing?
@Meyerweb Thanks for giving it a try! We want to bring together all the information that exists for a feature, and to cover the whole platform in the long term. Perhaps the most useful piece of additional data we're working on is usage stats for most features. For our own prioritization, a view like https://webstatus.dev/?q=-available_on%3Achrome is useful, in particular if we have developer signals, which we're exploring in https://github.com/web-platform-dx/developer-signals.
@foolip Hey Philip! I get the broad rationale (after all, I was part of some of those discussions) but the criteria for how features get listed/scored is opaque. To pick one example: Declarative Shadow DOM shows no compat scores due to “Insufficient test coverage.” despite having over 5,000 subtests, but the cap unit shows 100% coverage across the board thanks to all browsers passing all two subtests. Many other listed features just say --- for scores, with no explanation. Mystifying!
Add comment