fix(citations): repair 4 drifted performance sources#120
Draft
jdevalk wants to merge 1 commit into
Draft
Conversation
Rotating-slice citation check (this run: performance). Every change below was
verified by fetching the live URL today. None of these would fail the daily
external link job — each still returns 200, three of them by redirecting
somewhere the citation never claimed to point.
Spec discontinued — the cited document no longer exists:
- resource-hints: w3.org/TR/resource-hints/ now 301s off-host to
html.spec.whatwg.org/#linkTypes. The W3C Resource Hints spec was
discontinued and folded into the HTML Standard, which defines all five
link types (dns-prefetch, preconnect, preload, modulepreload, prefetch)
in section 4.6 Links. Cite WHATWG HTML instead. The body claimed "the W3C
Resource Hints specification defines four; HTML adds two more", which is
now wrong on both counts — corrected, and `updated` bumped because the
page's text changed.
Work moved to another SDO:
- no-vary-search: wicg.github.io/nav-speculation/no-vary-search.html now
serves a redirect notice ("This work has moved to the IETF HTTP working
group"). The live document is draft-ietf-httpbis-no-vary-search, adopted
by httpbis, -06 published 2026-07-06, intended for Proposed Standard.
That is a primary-source upgrade, not just a URL repair.
Article retired:
- http1-workarounds: web.dev/articles/performance-http2 301s off-host to
hpbn.co/http2/ (Grigorik's book). Replaced with MDN's Connection
management in HTTP/1.x, which carries the claims this page actually
makes — the ~6-connection limit, and that domain sharding is deprecated
and "even detrimental to performance" under HTTP/2 with connection
coalescing reverting it.
Unstable URL:
- server-timing: cited the editor's draft (w3c.github.io/server-timing) in
both the source list and an inline link. The published Working Draft at
w3.org/TR/server-timing/ is the same 2026-04-07 content and is the stable
URL; both cited anchors (#the-server-timing-header-field,
#privacy-and-security) exist there.
No `updated` bump on the other three: source hygiene with no change to what
the page says, matching #93/#94/#95/#101/#112.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Deploying specification-website with
|
| Latest commit: |
35babc5
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://98771a9d.specification-website.pages.dev |
| Branch Preview URL: | https://fix-performance-citation-dri.specification-website.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rotating-slice citation check from the daily standards scan. This run's slice:
performance/. Every URL below was fetched live today.The common thread: none of these would fail the daily external-link job. All four still return 200 — three of them by redirecting somewhere the citation never claimed to point. This is the semantic drift a link checker cannot see.
What changed
resource-hints— the cited spec was discontinuedhttps://www.w3.org/TR/resource-hints/now 301s off-host tohttps://html.spec.whatwg.org/#linkTypes. W3C Resource Hints was discontinued and folded into the WHATWG HTML Standard, whose §4.6 Links defines all five link types (#link-type-dns-prefetch,#link-type-preconnect,#link-type-preload,#link-type-modulepreload,#link-type-prefetch).The page's body also asserted "The W3C Resource Hints specification defines four; HTML adds two more" — wrong on both counts now. Rewritten to say all five live in HTML, and to name the wrong belief a reader arrives with (that Resource Hints is still a separate W3C spec). This is the only page whose text changed, so it is the only one with an
updatedbump.no-vary-search— work moved to the IETFhttps://wicg.github.io/nav-speculation/no-vary-search.htmlnow serves only a redirect notice: the work has moved to the IETF HTTP working group. The live document isdraft-ietf-httpbis-no-vary-search, "The No-Vary-Search HTTP Caching Extension" — adopted by httpbis, revision -06 published 2026-07-06, intended for Proposed Standard. A WICG editor's draft → adopted IETF WG draft is a primary-source upgrade, not just a URL repair.http1-workarounds— article retiredhttps://web.dev/articles/performance-http2301s off-host tohttps://hpbn.co/http2/(Grigorik's High Performance Browser Networking). web.dev retired the article; a citation labelled "web.dev — HTTP/2 and you" landing on a third-party book is not the source we claimed.Replaced with MDN — Connection management in HTTP/1.x, which carries the exact claims this page makes: the ~6-parallel-connection limit, and that domain sharding is deprecated, "no longer useful" under HTTP/2, "even detrimental to performance", with connection coalescing reverting it. That directly backs the page's
avoidstatus.server-timing— editor's draft → stable published URLCited
w3c.github.io/server-timingin both the source list and an inline link in Common mistakes. The published Working Draft athttps://www.w3.org/TR/server-timing/is the same 2026-04-07 content and is the stable URL; both cited anchors (#the-server-timing-header-field,#privacy-and-security) were confirmed present there.w3c.github.io/server-timing→w3.org/TR/server-timingStatus
No status changes. No page moves category.
updatedbumped onresource-hintsonly (its text changed); the other three are source hygiene with no change to what the page says, matching the convention in #93/#94/#95/#101/#112.Checks
npm run build✓ (164 pages) ·npm run lint✓ ·npm run format:check✓ ·npm run check:skill✓ (164 pages, 10 categories, MCP 2025-11-25, digest ✓)Note for the reviewer
resource-hintsis the borderline changelog case flagged in CLAUDE.md: one corrected sentence, not a substantive rewrite. I left the changelog alone — say the word if you'd rather it got achangedentry.🤖 Generated with Claude Code