Skip to content
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

Open
skyclouds2001 opened this issue Dec 19, 2024 · 3 comments
Open

Proposal: Remove IE-only features #837

skyclouds2001 opened this issue Dec 19, 2024 · 3 comments

Comments

@skyclouds2001
Copy link
Contributor

skyclouds2001 commented Dec 19, 2024

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

@skyclouds2001 skyclouds2001 added the needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. label Dec 19, 2024
@skyclouds2001 skyclouds2001 changed the title Remove all IE-specified features Remove IE-only features Jan 18, 2025
@skyclouds2001 skyclouds2001 changed the title Remove IE-only features Proposal: Remove IE-only features Jan 25, 2025
@pepelsbey
Copy link
Member

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.

@skyclouds2001
Copy link
Contributor Author

skyclouds2001 commented Feb 4, 2025

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

@bsmth
Copy link
Member

bsmth commented Feb 18, 2025

@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?

@bsmth bsmth removed the needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. label Feb 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants