-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Can a feature be experimental and deprecated at the same time? #1305
Comments
I think that if a feature is deprecated, it can't be experimental. It went out of experimental when it got deprecated. |
Out of curiosity, I checked it out and it looks like there are 57 features that are marked as both experimental and deprecated (source for generating this list):
|
I think there are cases where these both apply. Consider an API which was experimental, stayed in that state long enough that some sites started to deploy using it, and then the API was abandoned and became deprecated. If you remove the "experimental" label, it suggests that the API was finalized then later obsoleted. An API that's both experimental and deprecated is one that was never a finished/widely adopted API, but was shipped in at least one browser before later being deprecated. Consider things like RTCPeerConnection.addStream(). This method was removed while WebRTC was still in an unstable state, so it was experimental, but is now also obsolete. Another example: the original implementation of Custom Elements, which was in fact shipped in Chrome for a short time. That was an experimental API, since deprecated. Removing the "experimental" label suggests that it was a finished API that has become deprecated. |
I agree with @a2sheppy on this one, and suggest that |
Sounds like this didn't confuse more people over the last year, so I'm closing this and setting both to true remains allowed. |
I'm wondering if it should be valid to have features marked as
experimental: true
anddeprecated: true
at the same time.Currently, the MDN compat tables display icons when a feature is
deprecated: true
,experimental: true
orstandard_track: false
.The banners on top of MDN pages are not yet shown depending to the data we have in this data set, but added manually. We will likely change that to be automated based on the compat data soon.
Now, I'm wondering if
experimental: true
anddeprecated: true
shouldn't be ruling each other out.https://developer.mozilla.org/en-US/docs/Web/API/AnimationEvent/initAnimationEvent#Browser_compatibility
If this doesn't make sense, we could add validation that forbids experimental and deprecated being true at the same time. Thoughts?
The text was updated successfully, but these errors were encountered: