- From: Tab Atkins Jr. <notifications@github.com>
- Date: Wed, 20 Jan 2021 10:42:42 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 20 January 2021 18:42:54 UTC
In the section on requests, there are, at current count, 39 separate fields "associated with" a request. Some of those appear to be things the spec firing off a request would set; some of them appear to be things the fetch machinery would set; some of them are unclear. Several of them have notes giving some guidance on what they're for; several of these notes aren't sufficient for me to actually understand what the field is for or how to use it; about half of the fields don't have notes at all, leaving me to guess at the purpose and intended use of the field from the name. All in all, this means that I have no real clue what I'm supposed to do to, say, make CSS's `@import` use the Fetch machinery. Instead I have to ask Anne or Domenic to tell me how to do it, or try to hunt down a spec that's hopefully using best practices and cargo-cult their usage, hoping that they're not doing something odd that doesn't apply to my case. Since the stated point of Fetch is to allow specs to use a consistent, unambiguous machinery for processing requests and responses, it would be very useful to have explicit guidance given in the spec about how to actually use Fetch. -- 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/1143
Received on Wednesday, 20 January 2021 18:42:54 UTC