Skip to content

Conversation

@annevk
Copy link
Member

@annevk annevk commented Jan 14, 2026

While it is less likely you can attack a 416, it's probably good to stay consistent.

  • At least two implementers are interested (and none opposed):
    • Chromium presumably
  • Tests are written and can be reviewed and commented upon at:
  • Implementation bugs are filed:
    • Chromium: …
    • Gecko: …
    • WebKit: …
  • MDN issue is filed: N/A
  • The top of this comment includes a clear commit message to use.

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


Preview | Diff

While it is less likely you can attack a 416, it's probably good to stay consistent.
@yoshisatoyanagisawa
Copy link

lgtm.

annevk added a commit to web-platform-tests/wpt that referenced this pull request Jan 17, 2026
See whatwg/fetch#1907 for context.

We use an image instead of JavaScript as JavaScript requires a 2xx status whereas images don't care.

Also remove a redundant null check from useStoredRangeResponse() and a redundant catch() elsewhere.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants