Re: [fetch] Moar hyphens (#63)

> "image request context"

So yeah If we were to hyphenate that one, we'd need to also hyphenate "worker request context", "navigation request context", and "client request context".

But I think it would be wrong to do, e.g., "image-request context", because the shared term in all cases is "request context" (not just context), and "image", "worker", "navigation", and "client" here are all modifying/qualifying "request context". That is, there are all describing different types of request contexts.

So if were were to add any hyphen at all for these cases, it should probably be to hyphenate "request-context" so that we'd have "image request-context", etc.

"worker request context" seems clear enough without a hyphen, even in isolation, but reading "image request context" in isolation, it's ambiguous (to some readers at least) whether it means "a context for an image request" (in which case it would better be "image-request context") or "a request context for an image", in which case "image request-context" makes it more clear that's what it means.

I realize some of this sorta gets to the point of splitting hairs, but that's kind of what specs are about anyway.

So, all that said, do you think we should make it "request-context" consistently?

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/63#issuecomment-119135652