whatwg / whatwg/fetch

Request.destination and the empty string

Open
#765 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

clarification
Dominant language
HTML
Stars
2.3k
Forks
403
Avg merge
21h 16m
Merged PRs (30d)
4

Description

The spec says that the default value of destination is the empty string, but never defines explicitly what should happen if it is in fact the empty string. The closest I can find is the exemplar table that comes a couple of paragraphs later, and it does not clearly explain what the meaning of "" is for destination.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read the Request.destination definition in the linked Fetch Standard section, then compare it with the nearby exemplar table. Clarify explicitly what an empty destination string means and ensure the wording is consistent with the table.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
documentation, web-dev
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.