Skip to content

compute-baseline: Can features be baseline when they don't have a specification? #1497

@Elchi3

Description

@Elchi3

Not sure if this is intended behavior.

If you compute the status for ShadowRoot.elementFromPoint and ShadowRoot.elementsFromPoint:

import { computeBaseline } from "compute-baseline";

console.log(
JSON.parse(computeBaseline({compatKeys: ["api.ShadowRoot.elementFromPoint", "api.ShadowRoot.elementsFromPoint"], withAncestors: false}).toJSON())
);

you get

{
  baseline: 'high',
  baseline_low_date: '2020-01-15',
  baseline_high_date: '2022-07-15',
  support: {
    chrome: '53',
    chrome_android: '53',
    edge: '79',
    firefox: '63',
    firefox_android: '63',
    safari: '11.1',
    safari_ios: '11.3'
  }
}

even though these two keys have no specification.

Issue for them to be specified: w3c/csswg-drafts#5886

Can features be baseline when they don't have a valid specification?

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature evolutionIssues/PRs for describing changing feature definitions over time (as opposed to support)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions