Should we define standards in how we deal with web platform features that are described by baseline?
Suggestion:
Baseline: widely available. This means the feature can be safely used without fallback
Baseline: newly available. This means the feature can be used but a fallback needs to be provided. Optionally, a ticket can be created to remove the fallback, once the feature enters "wide availability".
Should we define standards in how we deal with web platform features that are described by baseline?
Suggestion:
Example: Focus styles (https://github.com/swisspost/design-system/blob/main/packages/styles/src/mixins/_utilities.scss#L115) has a fallback for cases where
:focus-visible
is not supported. However, this feature has a baseline: widely available. The mixin is used in a lot of components and removing the fallback could simplify the code.