Expunge “HTMLObjectElement: typeMustMatch” #3655
Conversation
sideshowbarker
requested review from
chrisdavidmills
and removed request for
a team
sideshowbarker
force-pushed
the
sideshowbarker/typemustmatch-drop
branch
from
fe2dc61
to
40d5501
Compare
This change deletes the Web/API/HTMLObjectElement/typeMustMatch article, as well as expunging all references to it from other articles. The change also drops all mentions of the corresponding “typemustmatch” markup attribute for “object” elements. The history of typeMustMatch/typemustmatch is that it was added to the spec in 2011 in whatwg/html@4030e71 but never got implemented across browsers and never got adopted by web developers. So whatwg/html#4590 dropped it from the spec in 2019, and it's now just a footnote in the “Non-conforming features” section at https://html.spec.whatwg.org/obsolete.html#attr-object-typemustmatch So there's statistically near-zero content on the web that’s using typeMustMatch/typemustmatch, and there’s no value to continue documenting it in MDN.
sideshowbarker
force-pushed
the
sideshowbarker/typemustmatch-drop
branch
from
40d5501
to
e6e995e
Compare
This change deletes “typeMustMatch” from api/HTMLObjectElement.json and deletes “typemustmatch” from html/elements/object.json. The history of typeMustMatch/typemustmatch is that it was added to the spec in 2011 in whatwg/html@4030e71 but never got implemented across browsers and never got adopted by web developers. So whatwg/html#4590 dropped it from the spec in 2019, and it's now just a footnote in the “Non-conforming features” section at https://html.spec.whatwg.org/obsolete.html#attr-object-typemustmatch So there's statistically near-zero content on the web that’s using typeMustMatch/typemustmatch, and there’s no value to continue tracking support data for it in BCD. Related MDN content change: mdn/content#3655
This change deletes “typeMustMatch” from api/HTMLObjectElement.json and deletes “typemustmatch” from html/elements/object.json. The history of typeMustMatch/typemustmatch is that it was added to the spec in 2011 in whatwg/html@4030e71 but never got implemented across browsers and never got adopted by web developers. So whatwg/html#4590 dropped it from the spec in 2019, and it's now just a footnote in the “Non-conforming features” section at https://html.spec.whatwg.org/obsolete.html#attr-object-typemustmatch So there's statistically near-zero content on the web that’s using typeMustMatch/typemustmatch, and there’s no value to continue tracking support data for it in BCD. Related MDN content change: mdn/content#3655
|
Is the main page of this attribute intentionally still available online (https://developer.mozilla.org/en-US/docs/Web/API/HTMLObjectElement/typeMustMatch) ? Or was it maybe overlooked? Nonetheless, we might want to add a notice to this page. |
Thanks much for catching this. That page isn’t intentionally still available — it was deleted from the sources but for some reason didn’t yet get deleted from the production service. @mdn/core-dev is there some additional action I need to do in order for that page to be deleted in production? |
@sideshowbarker We had to temporarily disable the ability to remove deleted documents when performing deployments (due to a bug in how we handled archived content). Sorry for the inconvenience! For now, I'll manually delete https://developer.mozilla.org/en-US/docs/Web/API/HTMLObjectElement/typeMustMatch from our stage and production S3 buckets. |
|
@sideshowbarker @saibotk I started on this, then was diverted onto something else, but it's finally complete now (including invalidating the cache on our stage and prod CDN's) so now https://developer.mozilla.org/en-US/docs/Web/API/HTMLObjectElement/typeMustMatch is a 404. |
|
Thank you, glad that we could resolve this so quickly :) Now this cannot confuse others anymore |
This change deletes the https://developer.mozilla.org/en-US/docs/Web/API/HTMLObjectElement/typeMustMatch article, as well as expunging all references to it from other articles. The change also drops all mentions of the corresponding
typemustmatchmarkup attribute forobjectelements.The history of
typeMustMatch/typemustmatchis that it was added to the spec in 2011 in whatwg/html@4030e71 but never got implemented across browsers and never got adopted by web developers. So whatwg/html#4590 dropped it from the spec in 2019, and it's now just a footnote in the “Non-conforming features section” at https://html.spec.whatwg.org/obsolete.html#attr-object-typemustmatchSo there's statistically near-zero content on the web that’s using
typeMustMatch/typemustmatch, and there’s no value to continue documenting it in MDN.