- From: Ben Kelly <notifications@github.com>
- Date: Fri, 12 Feb 2021 08:55:24 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 12 February 2021 16:55:37 UTC
Hmm, I see your point. Thanks for helping me understand. It seems this could even happen within a single document if they want to pull different sprites out of the same svg (using my example from above). I guess sw's that care about this could always strip the fragment themselves, but that seems non-ergonomic. We could provide an option to auto-strip at put() or match() time. Or an option to opt-out of auto-strip at put() or match() time. Or, as you suggest, provide a way to specify the fragment at match() time either through request url or an option. Or go with your recommendation to always use the FetchEvent.request.url fragment if present. Keeping the status quo of the FetchEvent.request.url fragment seems maybe best for now. If we do that, though, the fragment would be preserved on cache_storage response.url? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/505#issuecomment-778312623
Received on Friday, 12 February 2021 16:55:37 UTC