What problems would this solve? =============================== On many MDN pages, a writer used the title "Specification", because there is only one. The parser scrapes these as specification sections, but warns on the id and name "Specification". Who would use this? =================== MDN staff cleaning pages for the import process What would users see? ===================== MDN staff would not see id="Specification" as an error What would users do? What would happen as a result? =================================================== MDN staff would focus on harder data issues Is there anything else we should know? ====================================== An convert process is planed to automatically switch to API-backed specification tables, and an ID of "Specifications" was going to be used to identify this section. However, the convert process can instead be made more flexible, and do the conversion to a standard <h2>.
Severity: normal → enhancement
OS: Other → All
Commit pushed to master at https://github.com/mozilla/web-platform-compat https://github.com/mozilla/web-platform-compat/commit/011178885932904e93f9be524ce0298f43f9ca50 fix bug 1139433 - Allow id="Specification" in <h2> In specification <h2>, allow standard "Specifications" and alternate "Specification".
Status: UNCONFIRMED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.