This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 25759 - Add a 'download' context to Fetch?
Summary: Add a 'download' context to Fetch?
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: Fetch (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: Unsorted
Assignee: Anne
QA Contact: sideshowbarker+fetchspec
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-18 09:42 UTC by Mike West
Modified: 2014-05-18 13:59 UTC (History)
1 user (show)

See Also:

Attachments

Description Mike West 2014-05-18 09:42:49 UTC 
http://fetch.spec.whatwg.org/#requests

[[
associated context, which is one of
]]

It's unclear which context downloads (via `<a download ...>` for instance) would fall into. I'd suggest we add one.

In order to define mixed content blocking, we almost certainly need to separate 'content-disposition'-driven downloads from 'navigate' (which we can only do after we have the headers, of course). We can distinguish '<a download ...>' requests before making the request; it would be nice to do so.