Skip to content

Set request's initiator and destination to empty string in cache.addA…#1822

Merged
yoshisatoyanagisawa merged 2 commits intow3c:mainfrom
yoshisatoyanagisawa:cache_addall
Apr 9, 2026
Merged

Set request's initiator and destination to empty string in cache.addA…#1822
yoshisatoyanagisawa merged 2 commits intow3c:mainfrom
yoshisatoyanagisawa:cache_addall

Conversation

@yoshisatoyanagisawa
Copy link
Copy Markdown
Collaborator

@yoshisatoyanagisawa yoshisatoyanagisawa commented Apr 8, 2026

As pointed out in #1718, "fetch" is not a valid value for a request's initiator, and "subresource" is not a valid destination in the Fetch specification.

Following the discussion in the issue, cache.addAll() should function the same as if a script ran fetch() directly. Therefore, both initiator and destination should be set to the empty string.

Fixes #1718


Preview | Diff

…ll() (w3c#1718)

As pointed out in w3c#1718, "fetch"
is not a valid value for a request's initiator, and "subresource" is not
a valid destination in the Fetch specification.

Following the discussion in the issue, cache.addAll() should function
the same as if a script ran fetch() directly. Therefore, both initiator
and destination should be set to the empty string.

This updates the Cache/addAll algorithm steps in the specification.

Fixes w3c#1718
@yoshisatoyanagisawa
Copy link
Copy Markdown
Collaborator Author

@wanderview Will you review this?
Thank you.

Remove setting initiator and destination to empty string.
@yoshisatoyanagisawa yoshisatoyanagisawa merged commit d04904e into w3c:main Apr 9, 2026
2 checks passed
@yoshisatoyanagisawa yoshisatoyanagisawa deleted the cache_addall branch April 9, 2026 02:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Request's initiator can't be "fetch"

2 participants