-
Notifications
You must be signed in to change notification settings - Fork 192
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
Proposal: Remove IE-only features #837
Comments
The only concern here is that IE-only features won’t be linted or considered proper CSS in all tools that use mdn/data, like CSSTree, ESLint’s CSS linter, maybe some other tools, too. Even with IE gone, there’s still some CSS code left. |
it is true that some code may still existed IE-only features, removing this could break some code, that's why this should be a break change but we should consider when and how to remove these features, to indicate developers not to use these old features in new code and remove these from old code; to be consistent with BCD and web docs after all, I think there should be a rule in mdn/data about removing features that is not supported, deprecated or non-standard |
@skyclouds2001 we discussed this again, and these entries are still used by downstream projects (mentioned by Vadim above) who expressed interest in keeping the data intact, so we can leave as-is but essentially freeze any maintenance on them. Does that make sense? |
What information was incorrect, unhelpful, or incomplete?
for bcd and mdn docs, info about those IE-specified feature are all removed due to the retirement of Internet Explorer
the same thing should also be done in mdn/data repo
What did you expect to see?
remove all IE-specified features
Do you have any supporting links, references, or citations?
Do you have anything more you want to share?
No response
The text was updated successfully, but these errors were encountered: