Synchronize with BCD v5.5.6

[OnkarRuikar]

BCD release v5.5.6

/cc @queengooborg @sideshowbarker

[github-actions]

Preview URLs (11 pages)

• /en-US/docs/Web/API/HTMLMediaElement/seekToNextFrame
• /en-US/docs/Web/API/HTMLMediaElement
• /en-US/docs/Web/API/LargestContentfulPaint/element
• /en-US/docs/Web/API/LargestContentfulPaint/id
• /en-US/docs/Web/API/LargestContentfulPaint/loadTime
• /en-US/docs/Web/API/LargestContentfulPaint/renderTime
• /en-US/docs/Web/API/LargestContentfulPaint/size
• /en-US/docs/Web/API/LargestContentfulPaint/toJSON
• /en-US/docs/Web/API/LargestContentfulPaint/url
• /en-US/docs/Web/API/LargestContentfulPaint
• /en-US/docs/Web/CSS/ray

Flaws (13)

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

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

• macros:
  • /en-US/docs/Web/API/HTMLMediaElement/played does not exist
  • /en-US/docs/Web/API/HTMLMediaElement/preload does not exist
  • /en-US/docs/Web/API/HTMLMediaElement/seeking does not exist
  • /en-US/docs/Web/API/MediaController does not exist
  • /en-US/docs/Web/API/MediaController does not exist
  • and 7 more flaws omitted

---

URL: /en-US/docs/Web/CSS/ray
Title: ray()
Flaw count: 1

• macros:
  • wrong xref macro used (consider changing which macro you use)

[teoli2003]

👍

[dipikabh]

Hi @OnkarRuikar, I am surprised to see the update to the css/ray file here, especially because the same changes were merged via #31514 on Jan 10, just a couple of days before #31694, merged Jan 13.

Could it be because some automated BCD process did not pick up the latest content files?

cc @teoli2003

[OnkarRuikar]

Could it be because some automated BCD process did not pick up the latest content files?

This is because content PR got merged before BCD PR went live.

• On 10th BCDv5.5.5 went live
• On 11th your PRs go merged, then the bot synced BCDv5.5.5 with content at midnight reverting content changes.
• On 12th BCDv5.5.6 went live with the BCD PR.
• On 13th at midnight the bot synced v5.5.6 auto correcting the status.

The issue was your content change got merged(11th) before BCD PR went live in v5.5.6(12th).

[dipikabh]

Thanks for the breakdown of events, @OnkarRuikar.

On 11th your PRs go merged, then the bot synced BCDv5.5.5 with content at midnight reverting content changes.
On 13th at midnight the bot synced v5.5.6 auto correcting the status.

Ideally the bot should not have reverted the content updates. But if that's going to be the case, maybe we (especially those of us who update content for Firefox releases and assess an overall standing of the feature across browsers) should stop making the changes in mdn/content that are going to get sync'ed with a BCD release anyway (changes involving the banner macros and status field in front matter). I'll let the team know.