Proposal: Remove IE-only features

[skyclouds2001]

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?

• https://github.com/orgs/mdn/discussions/620
• https://death-to-ie11.com/
• Remove IE from BCD browser-compat-data#15333 for similar discussion in BCD
• Remove legacy Edge from BCD browser-compat-data#15619
• Remove IE-only prefixed APIs content#32929 for similar discussion in mdn docs
• Remove last specific pages about IE content#33012
• End of IE content#21718
• Remove legacy browsers support content#21721
• CSS content update: learn to support older browsers content#31473
• Remove references to IE content#32868
• Remove IE mentions 2, part 1 content#32861

Do you have anything more you want to share?

No response

[pepelsbey]

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]

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]

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