Lists of specs potentially worth checking - tidoust/web-features-standardization GitHub Wiki

Analyzing features in web-features

Features in web-features reference BCD keys (and/or specs directly). BCD keys can be used to collect a list of W3C specs that define concepts that compose a given feature. Comparing the Baseline status of the feature with the status of these specs on the W3C Recommendation track yields the following lists of specs that may be worth looking into.

Late incubations?

W3C specs that are still in incubation and that define well-supported features.

Specs linked to Baseline high features (21)
Specs linked to Baseline low features (6)
Specs linked to supported-though-not-yet-Baseline features (6)

Worth publishing as Candidate Recommendation?

W3C specs that are still Working Drafts and that define well-supported features.

Specs linked to Baseline high features (297)
Specs linked to Baseline low features (62)
Specs linked to supported-though-not-yet-Baseline features (84)

Interoperable specs with missing implementations?

W3C specs that are already Recommendation (or Proposed Recommendation) and that define not-so-well supported features.

Specs linked to supported-though-not-yet-Baseline features (3)
  • css-box-3 is referenced by BCD keys used to define feature overflow-clip-margin:
    • css.properties.overflow-clip-margin.border-box
    • css.properties.overflow-clip-margin.content-box
    • css.properties.overflow-clip-margin.padding-box
  • CSS2 is referenced by BCD keys used to define feature page-break-aliases:
    • css.properties.page-break-after.always
    • css.properties.page-break-after.auto
    • css.properties.page-break-after.avoid
    • css.properties.page-break-after.left
    • css.properties.page-break-after.right
    • css.properties.page-break-before.always
    • css.properties.page-break-before.auto
    • css.properties.page-break-before.avoid
    • css.properties.page-break-before.left
    • css.properties.page-break-before.right
    • css.properties.page-break-inside.auto
    • css.properties.page-break-inside.avoid
  • SVG11 is referenced by BCD keys used to define feature svg-discouraged:

Analyzing W3C specs in web-specs

To try to give a more complete perspective and highlight the need to have features defined in web-features, we can also map BCD keys directly to specs in web-specs, and consider that each spec defines a feature in itself for which we can compute a rough Baseline status from BCD support data. Running the same analysis with this new list of "features" yields the following lists of specs that may be worth looking into.

Late incubations?

W3C specs that are still in incubation and that define well-supported features.

Specs linked to Baseline low features (10)
Specs linked to supported-though-not-yet-Baseline features (7)

Worth publishing as Candidate Recommendation?

W3C specs that are still Working Drafts and that define well-supported features.

Specs linked to Baseline low features (15)
Specs linked to supported-though-not-yet-Baseline features (28)
⚠️ **GitHub.com Fallback** ⚠️