Re-generate extension API docs

Re-generate extension API docs

Fix broken </ br> tags in extension_api.json

For the zipfile changes:
TBR=kurrik

BUG=none
TEST=none

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

[gfeher, 2010-12-08 21:06:15]

Hi,
I see that you have modified the extension docs in:
http://codereview.chromium.org/5398002/diff/20001/chrome/common/extensions/do...

Your removed <br> tags are coming back if I re-generate the extension
documentation in trunk. We should either remove these <br>s from
extension_api.json or add them to the .html file, I don't know which is best.

Please review. Thanks,
Gábor

[kathyw, 2010-12-08 22:26:40]

I think what we really need to do is  change </br> to <br> in
extension_api.json, and then regenerate.

Background: For some reason, my doc generation always removes the
<br>, even though the <br>s are in the source. At one point I think I
removed them from extension_api.json, but they came back somehow.

But looking at extension_api.json, I see </br>, which should really be
<br> or maybe <br />. What makes it interesting is that our doc
generators have different reactions to the incorrect </br> tag, for
some reason.

-k-

On Wed, Dec 8, 2010 at 1:06 PM,  <gfeher@chromium.org> wrote:
> Reviewers: kathyw,
>
> Message:
> Hi,
> I see that you have modified the extension docs in:
>
http://codereview.chromium.org/5398002/diff/20001/chrome/common/extensions/do...
>
> Your removed <br> tags are coming back if I re-generate the extension
> documentation in trunk. We should either remove these <br>s from
> extension_api.json or add them to the .html file, I don't know which is
> best.
>
> Please review. Thanks,
> Gábor
>
> Description:
> Re-generate extension API docs
>
> Sync the html docs of the extension API with extension_api.json.
>
> BUG=none
> TEST=none
>
> Please review this at http://codereview.chromium.org/5563012/
>
> SVN Base: svn://svn.chromium.org/chrome/trunk/src
>
> Affected files:
>  chrome/common/extensions/docs/examples/extensions/chrome_search.zip
>  M chrome/common/extensions/docs/experimental.sidebar.html
>  M chrome/common/extensions/docs/samples.json
>
>
> Index: chrome/common/extensions/docs/examples/extensions/chrome_search.zip
> diff --git
> a/chrome/common/extensions/docs/examples/extensions/chrome_search.zip
> b/chrome/common/extensions/docs/examples/extensions/chrome_search.zip
> index
>
18cc6264963578801e2e0329579677420dfede2a..a38e561cb59742d4cb90df7c369e37d1a8fffebb
> 100644
> Binary files
> a/chrome/common/extensions/docs/examples/extensions/chrome_search.zip and
> b/chrome/common/extensions/docs/examples/extensions/chrome_search.zip differ
> Index: chrome/common/extensions/docs/experimental.sidebar.html
> diff --git a/chrome/common/extensions/docs/experimental.sidebar.html
> b/chrome/common/extensions/docs/experimental.sidebar.html
> index
>
09e6819d58ad88e49aa1946f15a78de2cde98d0f..727bf89006d5ce4feb43aca697224c4fd4ffb9fc
> 100644
> --- a/chrome/common/extensions/docs/experimental.sidebar.html
> +++ b/chrome/common/extensions/docs/experimental.sidebar.html
> @@ -952,7 +952,7 @@
>           <dd class="todo" style="display: none; ">
>             Undocumented.
>           </dd>
> -          <dd>'hidden' indicates sidebar is not defined for the specified
> tab (show was never called or hide() was called). Nothing is displayed for
> this sidebar.'shown' means sidebar is defined for the specified tab; mini
> tab is displayed for this sidebar. Sidebar UI is either collapsed or
> displaying a content of some other extension's sidebar.'active' indicates
> that sidebar is defined for the specified tab; sidebar UI is expanded and
> displaying this sidebar's content.</dd>
> +          <dd>'hidden' indicates sidebar is not defined for the specified
> tab (show was never called or hide() was called). Nothing is displayed for
> this sidebar.<br>'shown' means sidebar is defined for the specified tab;
> mini tab is displayed for this sidebar. Sidebar UI is either collapsed or
> displaying a content of some other extension's sidebar.<br>'active'
> indicates that sidebar is defined for the specified tab; sidebar UI is
> expanded and displaying this sidebar's content.</dd>
>           <dd style="display: none; ">
>             This parameter was added in version
>             <b><span></span></b>.
> Index: chrome/common/extensions/docs/samples.json
> diff --git a/chrome/common/extensions/docs/samples.json
> b/chrome/common/extensions/docs/samples.json
> index
>
e6eede3ce9015302299943a31ff86dfaab3c7f3f..2efbc41fd0c7e0f0474a7146af68c175bb55b3b0
> 100644
> --- a/chrome/common/extensions/docs/samples.json
> +++ b/chrome/common/extensions/docs/samples.json
> @@ -404,7 +404,7 @@
>         "background.html",
>         "manifest.json"
>       ],
> -      "source_hash": "1b58516fac8ed4dc97854e0bccb286a77e829a64",
> +      "source_hash": "027409688a677867e3f2fcbc530ceac904ccedea",
>       "zip_path": "examples/extensions/chrome_search.zip"
>     },
>     {
>
>
>

[gfeher, 2010-12-08 23:11:38]

I went for <br> because there are no slashes in the output html, even if I write
<br /> in the input .json.

If you can, please check if your build is still dropping the <br>s. (I was using
Linux.)

[kathyw, 2010-12-08 23:46:10]

LGTM

I use Linux, too, but I take some shortcuts that make my environment a bit
different. The <br>s show up in the output, though, so we're good.