Re: [fetch] Mechanism to indicate "destination context" (#64)

>> Yes.. but I'm not sure what you're trying to point out here?

> Well, is the processing model for that defined?

Ah, as in, the processing model for matching pre{fetch,load,render} responses with requests? Yes, this is an open issue: http://w3c.github.io/preload/#matching-responses-with-requests. That said, I don't think this is a blocking issue for this discussion.

> Is that matching algorithm defined somewhere?

I was thinking "regexp", but I guess that's unnecessary. A simpler version:

* Else, if the request contains type attribute, let value be the first matching statement whose value is a substring of request's type:
  * "image"
    * `image/png,image/svg+xml,image/*;q=0.8,*/*;q=0.5`
  * "xhtml", or "html", or "xml"
    * `text/html,application/xhtml+xml,application/xml;q=0.9,*`
  * "css"
    * `text/css,*/*;q=0.1`
  * otherwise, default to
     * `*/*`

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