Update specs and standard status of Speculation Rules API

[tunetheweb]

Description

Speculation Rules is on standards track, and prefetch has already be integrated into HTML spec (see whatwg/html#11426)

Motivation

MDN incorrectly lists this as non-standard.
It should be "experimental" as only Chromium implements it, but not non-standard as it is on standards track.

Additional details

See: whatwg/html#11426

Related issues and pull requests

Depends on:

• BCD update: Update Speculation Rules data with specs and Webview support browser-compat-data#27935

(I know some of this should be auto-copied across but never remember which to update and had to make other changes anyway so figured I'd do all the updates).

[github-actions]

Preview URLs

• /en-US/docs/Web/API/Speculation_Rules_API

Flaws (2)

URL: /en-US/docs/Web/API/Speculation_Rules_API
Title: Speculation Rules API
Flaw count: 2

• unknown:
  • Error serializing baseline for numeric-seperators: missing field description``
  • Error serializing baseline for single-color-gradients: missing field description``

(comment last updated: 2025-09-29 10:51:56)

[chrisdavidmills]

@tunetheweb the status keys in the YAML header tend to be updated automatically at some point, as do the header banners. But there is more here to update, and there is no harm in updating them now.

Just a couple of bits, after which I think you're good to go.

[chrisdavidmills]

There is also an inline non-standard badge to remove from the activationStart property entry in the list at https://developer.mozilla.org/en-US/docs/Web/API/PerformanceNavigationTiming.

[tunetheweb]

Got this one already in c758491#diff-5f8941d9eeb6bdd909084f20a29fe19b4fad8448085434d803f1f8ab50b63d76 I think?

[bsmth]

Thanks, both!

@tunetheweb the status keys in the YAML header tend to be updated automatically at some point, as do the header banners. But there is more here to update, and there is no harm in updating them now.

I think it's probably best to wait for the BCD change to land so that any hand-written changes applied in this PR are not reverted in the meantime.

[chrisdavidmills]

Thanks, both!

@tunetheweb the status keys in the YAML header tend to be updated automatically at some point, as do the header banners. But there is more here to update, and there is no harm in updating them now.

I think it's probably best to wait for the BCD change to land so that any hand-written changes applied in this PR are not reverted in the meantime.

Sure thing, that makes sense.

[chrisdavidmills]

Approving, but as @bsmth says, let's wait until the BCD changes are in and schlurped up by the content renderer before publishing this.

[tunetheweb]

BCD PR (mdn/browser-compat-data#27935) has just been merged. Any ideas how long it'll take to filter through there? How often does that sync process run?

[bsmth]

BCD PR (mdn/browser-compat-data#27935) has just been merged. Any ideas how long it'll take to filter through there? How often does that sync process run?

Nice! It will typically run after each BCD release:

https://github.com/mdn/content/pulls?q=is%3Apr+Synchronize+with+BCD+

There should be a new release tomorrow, so this will propagate over within 24/48hrs?

[tunetheweb]

Cool. Will check in next couple of days and ping you all again after this branch is updated with that.

[bsmth]

@tunetheweb the following has just landed #41307

Do you want to pull in from main to see the delta?

[tunetheweb]

Done. And it’s down to just two changes. Could have saved myself a lot of effort waiting for that!

[bsmth]

Done. And it’s down to just two changes. Could have saved myself a lot of effort waiting for that!

Sorry about that, we should consider a warn somewhere in PRs that these are mostly automated now! Maybe our review companion can detect things like this.

Anyway, good to go now, so let's merge 👍🏻

[tunetheweb]

Ah I knew that was a risk! And not many as impatient as me not to just wait 😁 But good to know it’s even more automated than I thought for the future!