-
Notifications
You must be signed in to change notification settings - Fork 132
compute-baseline: Can features be baseline when they don't have a specification? #1497
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This is unclear from the definition in https://github.com/web-platform-dx/web-features/blob/main/docs/baseline.md#interoperable-low-status. The only mention of specs in the whole document is "The specification text contains discouraging language, such as a deprecation notice, obsolescence warning, or legacy tag" but the case where there is no spec isn't mentioned. I think we'll need to make a case-by-case judgment about this, and we haven't given these two keys a Baseline status yet, they're not part of any feature. |
fwiw, I see 310 IDs in BCD where Details
|
Abstractly, I think this is a step removed from computing a status: what feature would unspecified behavior be a part of? More concretely, unspecified behavior wouldn't have a reportable status because it wouldn't be part of a web-features feature. And even if it were, how would we be able to review the status that would result, if what "should" happen is indeterminate? Eventually Pragmatically, I suppose that unspecified but interoperable behavior could be included in a feature, as it would be a de facto standard. But I suspect the exception would be easy to make, because it'd be very likely that a proposal exists to specify that behavior. (And for unspecified single-engine behaviors, I suppose we could consider some kind of "unspecified" status to live alongside Baseline. We'll probably want to have some sort of deprecated or discouraged status as well, so developers can understand support in that context.) |
Not sure if this is intended behavior.
If you compute the status for ShadowRoot.elementFromPoint and ShadowRoot.elementsFromPoint:
you get
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?
The text was updated successfully, but these errors were encountered: