[Extensions] Replace the developer_private.js extern with the autogenerated one

[Extensions] Replace the developer_private.js extern with the autogenerated one

Automatic extern generation has gotten to the point where it yields a better
result than the somewhat hand-modified version (Yay!). Use the generated one
in the closure compiler externs.

BUG=469920
Committed: https://crrev.com/5ed4724796d73dde8d2881181fc480d7f087f6bd
Cr-Commit-Position: refs/heads/master@{#322672}

[Devlin, 2015-03-26 20:29:42]

rdevlin.cronin@chromium.org changed reviewers:
+ dbeam@chromium.org

[Dan Beam, 2015-03-26 20:36:00]

¡lgtm!

https://codereview.chromium.org/1010083008/diff/1/third_party/closure_compile...
File third_party/closure_compiler/externs/developer_private.js (right):

https://codereview.chromium.org/1010083008/diff/1/third_party/closure_compile...
third_party/closure_compiler/externs/developer_private.js:264: *  
runtime_errors: !Array<*>,
:_(

https://codereview.chromium.org/1010083008/diff/1/third_party/closure_compile...
third_party/closure_compiler/externs/developer_private.js:416: * @param
{function(boolean):void=} callback Called with the boolean result,
:-)

https://codereview.chromium.org/1010083008/diff/1/third_party/closure_compile...
third_party/closure_compiler/externs/developer_private.js:487: * folder.
ideally these would be 4\s indented, but whatevs

https://codereview.chromium.org/1010083008/diff/1/third_party/closure_compile...
third_party/closure_compiler/externs/developer_private.js:487: * folder.
do we wanna even bother wrapping externs?  might as well just let 'em run.

[Devlin, 2015-03-26 22:36:36]

https://codereview.chromium.org/1010083008/diff/1/third_party/closure_compile...
File third_party/closure_compiler/externs/developer_private.js (right):

https://codereview.chromium.org/1010083008/diff/1/third_party/closure_compile...
third_party/closure_compiler/externs/developer_private.js:264: *  
runtime_errors: !Array<*>,
On 2015/03/26 20:36:00, Dan Beam wrote:
> :_(

Sad, but correct - it's declared as an "any" in the idl.  On the upside, though,
it's deprecated!  (Relatedly, I'm going to try and reach out to Spark/ADT once
all the churn is over, and get them to move off the deprecated methods.  Since
those are the only two using this api [apart from chrome://extensions now], we
should be able to remove the deprecated things.)

https://codereview.chromium.org/1010083008/diff/1/third_party/closure_compile...
third_party/closure_compiler/externs/developer_private.js:487: * folder.
On 2015/03/26 20:36:00, Dan Beam wrote:
> ideally these would be 4\s indented, but whatevs

Y'know, it was starting to bother me too.  Since it wasn't really relevant to
making the extern correct, I didn't worry about it, but let's actually make this
right.  And I think we should try wrapping externs.  It's nice to have them be
human-readable.

[Devlin, 2015-03-27 21:25:22]

Patchset #2 (id:20001) has been deleted

[Devlin, 2015-03-27 23:16:41]

https://codereview.chromium.org/1010083008/diff/1/third_party/closure_compile...
File third_party/closure_compiler/externs/developer_private.js (right):

https://codereview.chromium.org/1010083008/diff/1/third_party/closure_compile...
third_party/closure_compiler/externs/developer_private.js:487: * folder.
On 2015/03/26 22:36:36, Devlin wrote:
> On 2015/03/26 20:36:00, Dan Beam wrote:
> > ideally these would be 4\s indented, but whatevs
> 
> Y'know, it was starting to bother me too.  Since it wasn't really relevant to
> making the extern correct, I didn't worry about it, but let's actually make
this
> right.  And I think we should try wrapping externs.  It's nice to have them be
> human-readable.

And, now that https://codereview.chromium.org/1010603007/ landed, we can do
that.  Done.

[Devlin, 2015-03-27 23:16:45]

The CQ bit was checked by rdevlin.cronin@chromium.org

[Devlin, 2015-03-27 23:16:45]

The patchset sent to the CQ was uploaded after l-g-t-m from dbeam@chromium.org
Link to the patchset: https://codereview.chromium.org/1010083008/#ps40001
(title: "Updated")

[commit-bot: I haz the power, 2015-03-27 23:17:03]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1010083008/40001

[commit-bot: I haz the power, 2015-03-27 23:20:43]

Committed patchset #2 (id:40001)

[commit-bot: I haz the power, 2015-03-27 23:21:35]

Patchset 2 (id:??) landed as
https://crrev.com/5ed4724796d73dde8d2881181fc480d7f087f6bd
Cr-Commit-Position: refs/heads/master@{#322672}