Mirroring between statements (e.g., api.HTMLLinkElement.crossOrigin -> html.elements.link.crossorigin)

What would you like to see added to BCD?

It would good to be able to mirror between statements.

For example, html.elements.link.crossorigin probably actually matches api.HTMLLinkElement.crossOrigin (currently Chrome has different versions; I suspect this is a data bug, but I haven't checked), and it would be good to have them mechanically mirrored.

How impactful do you think this enhancement will be?

This will allow us to eliminate a lot of duplication between html and api that we have today, and fill in a variety of missing values in doing so. It also provides us with m

The statements in api are more likely to be kept up-to-date and accurate than those in html, as they can be derived by mdn-bcd-collector, whereas html requires manual curation, which often doesn't happen.

Do you have anything more you want to share?

See also https://github.com/mdn/browser-compat-data/issues/17911 for a related case between css.types and css.properties.

Also, see https://bugs.webkit.org/show_bug.cgi?id=236009#c9 for an example of someone being misled by the manually curated support tables being incomplete.

Start by comparing the example statements in api.HTMLLinkElement.crossOrigin and html.elements.link.crossorigin, then review the related css.types and css.properties issue linked in the report. Done means defining a workable mirroring approach that reduces duplication while addressing conflicts and keeping compatibility data consistent.