Description
(We might want to consider re-titling this to capture more broadly the rules for simplifying support statuses, but I'm starting with some narrow questions now.)
Some questions by way of https://github.com/web-platform-dx/feature-set/pull/78/files#r1129450273:
-
Should vendor prefixes count toward satisfying a definition of widely supported? For instance, given a feature group containing
alfa-property
, should support for-webkit-alfa-property
contribute toward satisfying support foralfa-property
and the group as a whole?If no (as suggested by @foolip), then how might we go about annotating the group to show that a workaround is available?
-
Should vendor prefixes ever be required for a definition of widely supported? For instance, given some feature group that contains
bravoInterface
, should the feature group ever require support forWebKitBravoInterface
to satisfy support for the group as a whole?An example of this would be
WebKitCSSMatrix
, which is specified as an alias toDOMMatrix
. Conformant implementations should implement the alias, but do we care? -
Should aliases ever be required for a definition of widely supported? For instance, given some feature group that contains
charlie-property
, should the feature group ever require support forlegacy-charlie-property
to satisfy support for the group as a whole?Examples include the legacy gap properties (
grid-column-gap
,grid-row-gap
,grid-gap
), which are now specified as aliases to the contemporary standard properties.