Remove unreachable preload destinations from match-preload-type

[KurtCattiSchmidt]

This change removes the extra, unreachable types listed for preload links under match-preload-type. They are unreachable because translate a preload destination happens first in the algorithm and does not continue for these extra types.

This change aligns the spec with existing implementations as well as MDN.

• At least two implementers are interested (and none opposed):
  • N/A - major engines already only support the limited set of preload types
• Tests are written and can be reviewed and commented upon at:
  • Existing tests cover this under wpt/preload, although the pass rate is low so some tests may need updating
• Implementation bugs are filed:
  • Chromium: N/A - this spec change matches current behavior
  • Gecko: N/A - this spec change matches current behavior
  • WebKit: N/A - this spec change matches current behavior
  • Deno (only for timers, structured clone, base64 utils, channel messaging, module resolution, web workers, and web storage): N/A
  • Node.js (only for timers, structured clone, base64 utils, channel messaging, and module resolution): N/A
• Corresponding HTML AAM & ARIA in HTML issues & PRs: N/A
• MDN issue is filed: N/A - MDN already reflects this behavior - https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Attributes/rel/preload
• The top of this comment includes a clear commit message to use.

(See WHATWG Working Mode: Changes for more details.)

Addresses #12068

---

/links.html ( diff )

[annevk]

In the algorithm header, can you replace "a string" with "a preload destination" (including link). That way we have a type assert as well.

[KurtCattiSchmidt]

In the algorithm header, can you replace "a string" with "a preload destination" (including link). That way we have a type assert as well.

Addressed @annevk

[annevk]

Nice!