What's the target browser support?

[gfellerph]

Target audience

Is it safe to assume this is the whole world?

Data source

What data should the decision be based on?

• statcounter (also caniuse.com): https://gs.statcounter.com/
• w3counter: https://www.w3counter.com/globalstats.php
• MDN browser-compat-data: https://github.com/mdn/browser-compat-data
• ...?

Decision framework

Is there some kind of framework or decision matrix that can be used for supporting discussions (for example if its above 90% supported on caniuse and is "baseline: widely available", the feature is ok to use without a fallback)?

References

• Baseline, https://developer.mozilla.org/en-US/docs/Glossary/Baseline/Compatibility
• A framework for evaluating browser support, https://www.joshwcomeau.com/css/browser-support/

[gregwhitworth]

This is a great question, for the Alpha version I would expect it to be supporting N-90 for "Stable". For example, when I look at data at our systems our customers span a MASSIVE spectrum across all browsers and so I'll probably lean into a N- approach for "stable" version. That doesn't mean that there can't be a branch that is targeting deprecation/removal of a polyfill. I'm interested in other people's opinions on this and I think it's important for us to have an initial stance but I also don't envision the matrix being massive. @bradfrost any chance in your history do you have a common browser support matrix we can use as a baseline. @gfellerph the other approach will be reviewing the component libs and design systems in our catalog and see what they do.

[sorvell]

Of course it's ideal if everyone can use this, but it can come at significant cost and potentially limit the value we can deliver to a sweet spot of users.

The unique value of this project is its close affiliation with actual browser standards and implementers. For that reason, I think it makes most sense to be future facing, leverage Javascript where appropriate, and use the latest implemented, standards track features.