You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We tend to define removed features along the lines of "removed in version 70" to mean that the feature worked in version 69 and was taken out, and no longer works, in version 70.
If I define this in the compatibility data as:
"version_added": 55,
"version_removed": "70",
This is displayed in the compatibility table on MDN as "55 – 70", which I would interpret as meaning the features available in version 55 up to and including version 70.
Therefore, should version_removed be stated as "the last version in which this feature was available" and in this case state it as "69" so it displays on MDN as "55-69"?
queengooborg
added
duplicate
Duplicate issues or pull requests. This one is closed in favor of the other issue or pull request.
invalid
Invalid issues or pull requests (wrong repo, spam, duplicates, etc.). This won't get merged. Sorry!
labels
Sep 16, 2019
queengooborg
removed
the
invalid
Invalid issues or pull requests (wrong repo, spam, duplicates, etc.). This won't get merged. Sorry!
label
Jun 21, 2021
We tend to define removed features along the lines of "removed in version 70" to mean that the feature worked in version 69 and was taken out, and no longer works, in version 70.
If I define this in the compatibility data as:
This is displayed in the compatibility table on MDN as "55 – 70", which I would interpret as meaning the features available in version 55 up to and including version 70.
Therefore, should
version_removed
be stated as "the last version in which this feature was available" and in this case state it as "69" so it displays on MDN as "55-69"?FYI @Elchi3 @ddbeck
The text was updated successfully, but these errors were encountered: