Skip to content

Linearize support version info #7403

@saschanaz

Description

@saschanaz

This is related to #1596.

Currently the version info becomes "parallel" when it comes to the legacy webkit aliases.

In flex-basis:

image

This is correct but the reader needs to get the information in "parallel" way:

  • 22+ just supports it
  • 49 added -webkit- alias
  • 44 added -webkit- alias behind flag
  • 18 supported behind flag and removed the flag in 28 (while the above confusingly does not say when the flag was removed)

This is needlessly complex, I think the version info should be linear per item:

  • 49 supports both the original property and the alias (could be helpful if alternative_name can indicate whether the original name also exists)
  • 44 added alias behind flag
  • 22 added the support
  • 18 supported the support behind flag (and forget when the flag was removed. Use version_removed only when the feature itself is removed)

Or even split them (but having two sources for prefixes (alternative_name or a subitem) is not very good):

  • flex-basis:
    • 22 added the support
    • 18-21 supported the support behind flag
  • -webkit-flex-basis:
    • 49 supports both the original property and the alias (could be helpful if alternative_name can indicate whether the original name also exists)
    • 44-48 added alias behind flag

Changes in #7401 mainly has this kind of complexity. What do you think?

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNice to have features.idleIssues and pull requests with no recent activityquestionIssues where a question or problem is stated and a discussion is held to gather opinions.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions