You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We could also be more specific if features rely on a specific API or browser features.
Why
We recently documented the features of each of our components with the intention of defining our core features and principles for helping decide whether to gracefully degrade on certain older browsers.
We'd like some quantitive data to confirm our assumptions about where things might break, and inform future decisions on where to "cut the mustard".
Who needs to work on this
Developer
Who needs to review this
Developer
Done when
Each card on the Trello board has been labelled with an ECMAScript version (eg: ES2017, ES2018)
[optional] Cards that rely on a specific API or browser feature have been labelled as such
These changes have been shared with the team
The text was updated successfully, but these errors were encountered:
Since we have a pretty set approach to cutting the mustard, and we're pretty sure all the current component features are compatible with ES6 browsers, I'm going to set this one as done.
What
Add labels to our internal "JS component features" Trello board to show the minimum ECMAScript version each feature relies on.
We could also be more specific if features rely on a specific API or browser features.
Why
We recently documented the features of each of our components with the intention of defining our core features and principles for helping decide whether to gracefully degrade on certain older browsers.
We'd like some quantitive data to confirm our assumptions about where things might break, and inform future decisions on where to "cut the mustard".
Who needs to work on this
Developer
Who needs to review this
Developer
Done when
The text was updated successfully, but these errors were encountered: