experimental.downloads extension api docs

chrome/common/extensions/docs/static/experimental.downloads.html

Index: chrome/common/extensions/docs/static/experimental.downloads.html
diff --git a/chrome/common/extensions/docs/static/experimental.downloads.html b/chrome/common/extensions/docs/static/experimental.downloads.html
new file mode 100644
index 0000000000000000000000000000000000000000..1bd6026ff2575b35bb1facd6b90988d59d16d789
--- /dev/null
+++ b/chrome/common/extensions/docs/static/experimental.downloads.html
@@ -0,0 +1 @@
+The downloads API allows you to programmatically initiate downloads, examine and monitor properties of downloads, and manipulate downloads.

[mkearney, 2012/03/02 01:56:07]

This should be wrapped in <p> tag.

[mkearney, 2012/03/02 01:56:07]

Is it too early to include an example of a use case here?

'Use this API to download URLs ... for example ...'

It might be a little early still.

[mkearney, 2012/03/02 01:56:07]

Can we move the information about the need to include any URL being downloaded
in the extension's manifest in the API static doc rather than in the method
description? 

[mkearney, 2012/03/02 01:56:07]

Do you want me to review the samples, or is it too early? If the samples are
going out at the same time, then what about including a example section with a
link to those samples?

[benjhayden, 2012/03/02 16:27:06]

Done.

[benjhayden, 2012/03/02 16:27:06]

Can I ask why? There are going to be several other methods, and the url
permission restriction will only apply to download(). I thought that this static
file should apply to the API as a whole.

[benjhayden, 2012/03/02 16:27:06]

Done.
Mihai reviewed download_links on its way in, but feel free to review it if you
like.

[benjhayden, 2012/03/02 16:27:06]

There's a sample extension.