Clarified the manifest example code. Added "version" description....

Clarified the manifest example code. Added "version" description.

TEST=none
BUG=none


Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=29905

[Kathy Walrath, 2009-10-23 06:02:13]

Please pay special attention to the new version section (bottom of the page).

[Aaron Boodman, 2009-10-23 06:13:41]

* You can get rid of the "icon" section. That is deprecated.

* The description of the permissions field reads awkwardly to me. What
about: " A permission can be either one of a list of known strings
(currently, either "tabs" or "bookmarks") or a match pattern, which
gives access to one or more hosts. Certain APIs in the extension
system require that you declare a permission in your manifest before
they can be used. These permissions are displayed to users before
installation, and requiring them helps limit damage if your extension
is exploited by malicious code." ... or something

---

The version section is correct!

- a

On Thu, Oct 22, 2009 at 11:02 PM,  <kathyw@google.com> wrote:
> Reviewers: Aaron Boodman,
>
> Message:
> Please pay special attention to the new version section (bottom of the
> page).
>
> Description:
> Clarified the manifest example code. Added "version" description.
>
> TEST=3Dnone
> BUG=3Dnone
>
>
> Please review this at http://codereview.chromium.org/326008
>
> SVN Base: svn://chrome-svn/chrome/trunk/src/
>
> Affected files:
> =A0M =A0 =A0 chrome/common/extensions/docs/manifest.html
> =A0M =A0 =A0 chrome/common/extensions/docs/static/manifest.html
>
>
>

[Kathy Walrath, 2009-10-23 07:00:42]

On 2009/10/23 06:13:41, Aaron Boodman wrote:
> * You can get rid of the "icon" section. That is deprecated.

Cool. Done.

> * The description of the permissions field reads awkwardly to me. 

I've rewritten it a bit. I tried to make it a little future proof (removing the
"currently", e.g.) and added some (hopefully reassuring) text about where they
(the developer, that is) would learn about permissions.