- From: Andrew Williams <notifications@github.com>
- Date: Wed, 19 Nov 2025 15:23:35 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 19 November 2025 23:23:39 UTC
@recvfrom commented on this pull request. > + <li><p><var>requestEnvironment</var>'s <a for="environment">creation URL</a> + <a for=url>equals</a> <var>request</var>'s <a for=request>current URL</a>, Hmm, what are your thoughts on this? In Chrome we implemented exact matching because that's how the media fetch breakage we were aiming to work around presented itself (when navigating to a blob URL with a media mime type, the media element src is always exactly the URL you navigated to, fragment included if present)... But for other cases I could see ignoring the fragment identifier be a reasonable thing to do. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/pull/1879#discussion_r2543860845 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/pull/1879/review/3485104891@github.com>
Received on Wednesday, 19 November 2025 23:23:39 UTC