Re: [fetch] Initializing context/content specific fetch defaults (#43)

@annevk nice. A couple of questions...

1. Can we add a note indicating that the specified Accept values are recommended values, and **should be extended** by the user agent to match the supported types - e.g. WebP, JPEGXR, and so on.
1. Can we also extend this mechanism to cover transport priorities? E.g. navigation requests have higher priority than CSS/JS (critical resources), which have higher priority than images, and so on.
  * Similar to Accept, the priority values vary for each UA and protocol in use (HTTP/1.1 vs HTTP/2). Perhaps we can simply indicate that the user agent _should_ set the transport priority based on indicated context?

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