Skip to content

Conversation

@recvfrom
Copy link
Contributor

@recvfrom recvfrom commented Nov 14, 2025

Implements the fetch spec side of bypassing partitioning when a top-level blob URL document attempts to fetch itself. For more info see: w3c/FileAPI#210

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


Preview | Diff

Implements the fetch spec sid of bypassing partitioning when
a top-level blob URL document attempts to fetch itself. For
more info see: w3c/FileAPI#210
fetch.bs Outdated
<ul class=brief>
<li><p><var>global</var> is a {{Window}} object;

<li><p><var>global</var>'s <a for=Window>navigable</a> is not null;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if there are cases where this would be null and you can get this far into a fetch. Hmm.

Copy link
Member

@domfarolino domfarolino Nov 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Specifically where client is non-null but not associated with a Window object? Would worker fetches count here? Maybe even navigation requests themselves, with their reserved client machinery...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I mirrored this off of the logic in https://fetch.spec.whatwg.org/#populate-request-from-client, but I'm not certain that the cases there are possible here as well...

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