chrome/common/extensions/docs/static/experimental.downloads.html - Issue 9452019: experimental.downloads extension api docs

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: chrome/common/extensions/docs/static/experimental.downloads.html

Issue 9452019: experimental.downloads extension api docs (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src

Patch Set: ... Created 8 years, 9 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch | Annotate | Revision Log

OLD	NEW
(Empty)
	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. 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 cas 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 incl 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 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. Show quoted text On 2012/03/02 01:56:07, mkearney wrote: > This should be wrapped in <p> tag. Done. benjhayden 2012/03/02 16:27:06 Can I ask why? There are going to be several other Show quoted text On 2012/03/02 01:56:07, mkearney wrote: > 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? 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, Show quoted text On 2012/03/02 01:56:07, mkearney wrote: > 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? 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. Show quoted text On 2012/03/02 01:56:07, mkearney wrote: > 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. There's a sample extension.
OLD	NEW

« chrome/common/extensions/api/experimental.downloads.json ('K') | « chrome/common/extensions/docs/samples.json ('k') | no next file » | no next file with comments »