Add informative section on legacy constructs #506
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
domenic
reviewed
Jan 4, 2018
index.bs
Outdated
| by <a href="https://github.com/heycam/webidl/issues/new?title=Intent%20to%20use%20a%20legacy%20WebIDL%20construct">filing an issue</a> | ||
| before proceeding. | ||
|
|
||
| Legacy WebIDL constructs are not deprecated unless they are specifically marked as such. |
There was a problem hiding this comment.
I don't think this paragraph is helpful because we don't have any notion of "deprecated" on the web platform. So this is just confusing.
If you want to talk about "removal" that's a separate story.
domenic
approved these changes
Jan 4, 2018
index.bs
Outdated
| before proceeding. | ||
|
|
||
| Marking a construct as legacy does not, in itself, | ||
| imply that it is about to be removed form this specification. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I often see confusion about deprecation and legacy constructs. For example: KhronosGroup/WebGL#2566 (comment). I was also very confused by this when I started working on WebIDL.
This is an attempt at clarifying this. I'm not sure whether all advisements should just link to this section, be completely replaced by a link to it, or should simply co-exist as in this current PR. Thoughts welcomed.
Preview | Diff