Synchronize with BCD v7.3.9

[OnkarRuikar]

BCD release v7.3.9

/cc cc/ @bsmth @wbamberg

[github-actions]

Preview URLs (17 pages)

• /en-US/docs/Web/API/CSSFontFaceDescriptors
• /en-US/docs/Web/API/Document/ariaNotify
• /en-US/docs/Web/API/Document
• /en-US/docs/Web/API/Element/ariaNotify
• /en-US/docs/Web/API/Element
• /en-US/docs/Web/API/HTMLMediaElement/loading
• /en-US/docs/Web/API/HTMLMediaElement
• /en-US/docs/Web/API/HighlightRegistry/highlightsFromPoint
• /en-US/docs/Web/API/HighlightRegistry
• /en-US/docs/Web/API/PerformanceElementTiming/paintTime
• /en-US/docs/Web/API/PerformanceElementTiming/presentationTime
• /en-US/docs/Web/API/PerformanceElementTiming
• /en-US/docs/Web/API/PerformanceLongAnimationFrameTiming/paintTime
• /en-US/docs/Web/API/PerformanceLongAnimationFrameTiming/presentationTime
• /en-US/docs/Web/API/PerformanceLongAnimationFrameTiming
• /en-US/docs/Web/HTML/Reference/Elements/audio
• /en-US/docs/Web/SVG/Reference/Attribute/font-stretch

Flaws (3)

Note! 15 documents with no flaws that don't need to be listed. 🎉

Found an unexpected or unresolvable flaw? Please report it here.

URL: /en-US/docs/Web/API/Element
Title: Element
Flaw count: 1

• macros:
  • Macro domxref produces link /en-US/docs/Web/API/Element/getBoxQuads which doesn't resolve

---

URL: /en-US/docs/Web/API/HTMLMediaElement
Title: HTMLMediaElement
Flaw count: 2

• macros:
  • Macro domxref produces link /en-US/docs/Web/API/MediaController which doesn't resolve
  • Macro domxref produces link /en-US/docs/Web/API/MediaController which doesn't resolve

[Josh-Cena]

@OnkarRuikar btw, I think you should take Brian off the cc list.

[OnkarRuikar]

@OnkarRuikar btw, I think you should take Brian off the cc list.

Along with you, who should I add to the list? No one was there to merge v7.3.7. Had to scrap the PR and trigger v7.3.8.

[pepelsbey]

Looks good! Thank you 🙂

[pepelsbey]

Along with you, who should I add to the list? No one was there to merge v7.3.7. Had to scrap the PR and trigger v7.3.8.

I would suggest adding @mdn/content-team. There are other teams as well, which is more flexible than tagging specific people.

[Josh-Cena]

I'd say the assigned reviewer is a good baseline, because this does constitute a content change and could have complications when displayed to the reader.

[OnkarRuikar]

I would suggest adding @mdn/content-team. There are other teams as well, which is more flexible than tagging specific people.

@pepelsbey Without being the mdn organisation member on GitHub I can't tag @mdn/content-team .

I'd say the assigned reviewer is a good baseline

De facto the code owners have rarely approved or merged these PRs. Also, there is limited time frame to merge these PRs because BCD release happens every Friday or Saturday(weekend), in past on Tuesdays as well. We can't force everyone to merge before the next BCD release.
That is why looking for dedicated reviewers for such maintenance type of PRs. Some repo maintainer who glances at each content PR and issue ever;y morning.
How about the bcd person who does BCD release?