In #1146, we are tracking the replacement of the text of the Specifications section by information stored in mdn/browser-compat-data, under the spec_url entry.

For Web/API/* we have performed the first pass, that is sourcing it via the {{Specifications}} macros, as well as filing follow-up bugs under mdn/browser-compat-compat to complete missing data.

Two kinds of feature have lost their spec table: dictionaries (and typedef, enums) and non-standard features. Dictionaries will be handled when we revisit how we document them (a lot of pages will be merged into other, …)

This bug tracks the progress in improving the specification section of non-standard features in Web/API. There will be quite a lot of PR, and I want to be able to keep #1146 as an easy way to keep an eye on the progres on migration to the {{Specifications}} macro

In mdn/yari#4012 we have decided not to change the message given by yari, and in mdn/browser-compat-data#10971 to keep the spec_url field only for active specifications (and not for abandoned specifications).

What we may do to the different pages (depending of the specific context).

1. Removing the whole section
2. A text linking to the outdated spec (if the information there may be useful)
3. No link to the outdated spec but a pointer to a more modern spec
4. Other!!!

Let's try it. I'll link the different PR to this issue so that we have an overview of the work, the decisions taken in the different cases.