Remove documentation about Microsoft Extensions#18750
Remove documentation about Microsoft Extensions#18750queengooborg wants to merge 5 commits intomdn:mainfrom queengooborg:ms-extensions
Conversation
Preview URLs (14 pages)
Flaws (268)Note! 3 documents with no flaws that don't need to be listed. 🎉 URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
External URLs (16)URL: URL:
URL:
URL:
URL: URL: URL: URL:
URL: URL: (comment last updated: 2023-02-13 13:54:03) |
|
I must decline the request to review this. I don't know anything about MS extensions. |
|
No worries, @jpmedley! This is something that should probably be discussed during an MDN content planning meeting first anyways, before official review! |
|
I've converted this to a draft to make sure it is not merged before I add redirects where applicable, as requested during the MDN content planning meeting earlier today! Edit: there are no applicable redirects I can create, so I have not created any. |
estelle
left a comment
There was a problem hiding this comment.
I would like to keep Microsoft CSS Extensions around until IE is completely not supported. It's the only place that has a somewhat complete list and would prefer not to remove the resource until IE really is completely gone.
Unfortunately, I don't think that IE will ever be completely gone, or at least, not until 2029 due to Edge's "IE mode", and is still supported in enterprise editions of Windows 10. Windows 10 itself will be EOL in 2025 for all editions. I personally feel that documenting Internet Explorer-specific features will encourage developers to continue writing IE-compatible websites, which encourages continued use of IE, despite the fact it contains numerous security holes that will never be patched. At some point, we've got to rip this bandaid off, but I don't think we should wait until 2025 or 2029 to do it. |
|
This PR is too big. I think we might have consensus on a few bits here (I was about to propose to remove the MS gesture event pages). Maybe other features (CSS properties) should stay for a bit still. We need smaller PRs to discuss in more detail (as opposed to "remove everything"). Closing. |
|
I've reopened the PR but marked it as a draft instead, to show what needs to be done to remove this category. |
|
@schalkneethling Can you move this to a discussion? |
|
Pull requests can't be converted into discussions, but a new discussion can be created! |
|
Let's close this then. It will be easier to create new PRs than to merge main into this every 3 days for the next 6 months. |
|
Can we leave it open as a draft for the time being, please? |
There was a problem hiding this comment.
We can keep this as a draft if you want.
I don't think there is an agreement to merge this. We want to remove old IE data, but there is no consensus about when and how.
As @Elchi3 said, likely, some pages here can already be removed, but others not. As long as nobody has looked at each in detail and has demonstrated a consensus, we should not merge this.
The properties, methods, and attributes listed here are heterogenous and have different uses. We decided at the end of last Quarter (when we added the page-type YAML header) to keep them as it was unclear how useful they were. We really hesitated, but we decided not to force the move without a proper discussion, as there was no urgency.
I'm interested in seeing the reasons for removing the different groups of features. Example of points to discuss (there are likely more): are some of these features already deprecated in IE11, and superseded by newer features in that browser? In these cases, we should delete them. For other cases, for features without replacement, I think we should keep them for the time being.
I'm open to discussing all this, and I don't think this PR is appropriate as we don't know how we will proceed.
|
There are many other questions to answer here:
|
|
Thanks for doing the work, Vinyl! I'm happy to look at this PR in any state. Just wanted to set expectations that I don't think this PR is mergable as is. For actual removal it is just better to decide on the individual topics / feature sets. It's just too hard to decide on all of them at once. Also, maybe we want to set redirects and that is easier to do in smaller PRs, too. Example PR: Blob APIs: #20245 |
|
Hey folks! We discussed this and we're going to do the following:
|
|
This pull request has merge conflicts that must be resolved before it can be merged. |
Conflicts: files/en-us/_redirects.txt files/en-us/_wikihistory.json files/en-us/web/api/cssstyledeclaration/msgetpropertyenabled/index.md files/en-us/web/api/cssstyledeclaration/msputpropertyenabled/index.md files/en-us/web/api/document/mssitemodejumplistitemremoved_event/index.md files/en-us/web/api/document/msthumbnailclick_event/index.md files/en-us/web/api/element/msgesturechange_event/index.md files/en-us/web/api/element/msgestureend_event/index.md files/en-us/web/api/element/msgesturehold_event/index.md files/en-us/web/api/element/msgesturestart_event/index.md files/en-us/web/api/element/msgesturetap_event/index.md files/en-us/web/api/element/msgetregioncontent/index.md files/en-us/web/api/element/msinertiastart_event/index.md files/en-us/web/api/element/msmanipulationstatechanged_event/index.md files/en-us/web/api/element/msregionoverflow/index.md files/en-us/web/api/element/mszoomto/index.md files/en-us/web/api/htmlaudioelement/msaudiodevicetype/index.md files/en-us/web/api/htmlelement/mscandidatewindowhide_event/index.md files/en-us/web/api/htmlelement/mscandidatewindowshow_event/index.md files/en-us/web/api/htmlelement/mscandidatewindowupdate_event/index.md files/en-us/web/api/htmlmediaelement/mscleareffects/index.md files/en-us/web/api/htmlmediaelement/msinsertaudioeffect/index.md files/en-us/web/api/htmlvideoelement/index.md files/en-us/web/api/microsoft_extensions/index.md files/en-us/web/api/msgestureevent/index.md files/en-us/web/api/msmanipulationevent/index.md files/en-us/web/api/msmanipulationevent/initmsmanipulationevent/index.md files/en-us/web/api/mssitemodeevent/index.md files/en-us/web/api/mswriteprofilermark/index.md files/en-us/web/api/navigator/mslaunchuri/index.md files/en-us/web/api/touch/msmanipulationviewsenabled/index.md files/en-us/web/api/xmlhttprequest/mscaching/index.md files/en-us/web/api/xmlhttprequest/mscachingenabled/index.md files/en-us/web/css/@media/-ms-high-contrast/index.md files/en-us/web/css/media_queries/using_media_queries_for_accessibility/index.md files/en-us/web/css/microsoft_extensions/index.md files/en-us/web/events/index.md files/en-us/web/html/global_attributes/x-ms-acceleratorkey/index.md files/en-us/web/html/global_attributes/x-ms-format-detection/index.md
|
This pull request has merge conflicts that must be resolved before it can be merged. |
|
This pull request has merge conflicts that must be resolved before it can be merged. |
|
This removal project has now been taken care of in other PRs! |
This PR removes all of the documentation regarding Microsoft proprietary events, properties, etc. from MDN Web Docs. They can be removed per BCD's irrelevance guidelines, since they have been removed from Edge over two years ago, and have not been included in a browser version that has been released within the last five years. Related BCD PR: mdn/browser-compat-data#17120