The `as` values are defined as a Fetch destination. For scripts, the required `as` value is "script". For XHRs, it's currently the empty destination (so either an empty `as` or a missing one results in an XHR-like fetch). فاروش <https://faroush.com> On Friday, December 23, 2016 at 6:08:28 PM UTC+3:30 PhistucK wrote:
> Yes, I meant an as value for fetch/XMLHttpRequest, not the existence of > the attribute itself in specifications. :) > > > ☆*PhistucK* > > On Fri, Dec 23, 2016 at 4:14 PM, Yoav Weiss <[email protected]> wrote: > >> >> On Fri, Dec 23, 2016 at 10:07 AM PhistucK <[email protected]> wrote: >> >>> Right, thank you for the clarifications, I forgot about the >>> XMLHttpRequest versus script fetch differences for a second. >>> >>> I actually search for an as value and could not find it, I guess it is >>> not standardized yet. >>> >>> >> The `as` values are defined as a Fetch destination >> <https://fetch.spec.whatwg.org/#concept-request-destination>. For >> scripts, the required `as` value is "script". For XHRs, it's currently the >> empty destination (so either an empty `as` or a missing one results in an >> XHR-like fetch). >> >> We're currently debating <https://github.com/w3c/preload/issues/80> if >> that is the right thing to do, or it'd be better if XHRs/fetch() required >> an explicit value. >> > > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/8fb92469-fc8b-4e8a-ad2e-167203650689n%40chromium.org.
