Open esetnik opened 4 years ago
@esetnik great question – I'm thinking that it might be worthwhile to focus on 1) most popular, and 2) default mobile browsers for this, since one primary goal is mobile accessibility. Meaning, w.r.t. your question on the other issue, I think we could avoid IE11 support. It's below Opera right now in estimated usage for 2019, and not a default browser on Android or Apple phones. Thoughts?
My only consideration as to whether or not to support ie11 is that the demographic of our users are most likely not the earliest adopters of technology based on financial constraints and the age of the population so I would expect we will see more usage of older browsers than "most popular" lists report. Even at my work we see >3% usage on ie11 and we choose not to support it.
I think eliminating ie11 official support is probably something we can get away with, but we should probably polyfill for ie11 anyways and attempt to at least get the page to load even if the UX isn't great due to usage of newer browser features like flexbox and grid that don't work well on ie11.
For now can we use something like https://polyfill.io/v3/polyfill.min.js?features=default
to cover us without adding a lot of bloat to the bundle?
we can also use https://www.gatsbyjs.org/docs/browser-support/
Also should add linting config https://github.com/amilajack/eslint-plugin-compat #19
Come up with a list of browsers we’re trying to support and add required polyfills.