Consider linking to implementation bugs by using the BCD impl_url data

[captainbrosset]

Can the Web MIDI API be used across browsers? Not yet because Safari doesn't support it.
When it will be supported? Can people influence Safari's priorities to get it sooner than later? Impossible to know the answer to the former, but for the latter, developers can comment on the WebKit tracking bug that's very nicely listed at the bottom of the corresponding Can I Use entry (under the Resources section).

This is great, and I'm opening this issue to discuss doing the same (or similar) thing for Can I Use features that come from BCD.

BCD features come with per-browser data that includes a impl_url field which links to the corresponding tracking bugs.

Recent examples which I added to BCD:

• Masonry auto-flow: https://github.com/mdn/browser-compat-data/blob/main/css/properties/masonry-auto-flow.json#L14
• Temporal: https://github.com/mdn/browser-compat-data/blob/main/javascript/builtins/Temporal.json#L21
• Scroll-driven animations: https://github.com/mdn/browser-compat-data/blob/main/css/properties/scroll-timeline.json#L41
• CSS typed OM: https://github.com/mdn/browser-compat-data/blob/main/api/CSS.json#L51

Perhaps the simplest thing to do would be to populate the Resources section with these impl_url links, when they exist, for BCD-based entries on Can I Use.

[Fyrd]

Sounds like a good idea, thanks!