Update references to the extension messaging APIs to point to the "runtime"

Update references to the extension messaging APIs and lastError to point to
the "runtime" namespace rather than "extension" in docs and samples.


R=asargent@chromium.org
TBR=dgozman@chromium.org

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=175527

[not at google - send to devlin, 2013-01-03 18:10:56]

I noticed that presubmit tests were failing on resolving doc links to
extension.sendMessage (and a few others), so I just ran a find-replace over the
codebase for the APIs that were removed. This basically just updates docs and
samples.... and test data.

I also did a replacement for lastError, since I noticed that hadn't been moved
for the samples.

https://codereview.chromium.org/11745015/diff/1/chrome/common/extensions/api/...
File chrome/common/extensions/api/extension.json (left):

https://codereview.chromium.org/11745015/diff/1/chrome/common/extensions/api/...
chrome/common/extensions/api/extension.json:19: },
I don't think these actually need to be around still?

[asargent_no_longer_on_chrome, 2013-01-03 22:42:27]

LGTM w/ one needed fix in
chrome/test/data/extensions/api_test/stubs/content_script.js

https://codereview.chromium.org/11745015/diff/1/chrome/common/extensions/api/...
File chrome/common/extensions/api/extension.json (left):

https://codereview.chromium.org/11745015/diff/1/chrome/common/extensions/api/...
chrome/common/extensions/api/extension.json:19: },
On 2013/01/03 18:10:56, kalman wrote:
> I don't think these actually need to be around still?

Yeah, I guess we should remove them if we don't need them. The fact that I used
aliasing for backwards compatability probably means they don't need to be
present for API call args checking.

https://codereview.chromium.org/11745015/diff/12001/chrome/renderer/resources...
File chrome/renderer/resources/extensions/runtime_custom_bindings.js (right):

https://codereview.chromium.org/11745015/diff/12001/chrome/renderer/resources...
chrome/renderer/resources/extensions/runtime_custom_bindings.js:50: var port =
chrome.runtime.connectNative(
nice catch!

https://codereview.chromium.org/11745015/diff/12001/chrome/test/data/extensio...
File chrome/test/data/extensions/api_test/stubs/content_script.js (right):

https://codereview.chromium.org/11745015/diff/12001/chrome/test/data/extensio...
chrome/test/data/extensions/api_test/stubs/content_script.js:82: path !=
"runtime.lastError" &&
Should you have just removed this line, since there is a duplicate check one
line down?

[not at google - send to devlin, 2013-01-04 22:22:02]

Ok, finally got the trybots working (they weren't liking some DOS file endings,
ugh) so let's see how this goes.

https://codereview.chromium.org/11745015/diff/1/chrome/common/extensions/api/...
File chrome/common/extensions/api/extension.json (left):

https://codereview.chromium.org/11745015/diff/1/chrome/common/extensions/api/...
chrome/common/extensions/api/extension.json:19: },
On 2013/01/03 22:42:27, Antony Sargent wrote:
> On 2013/01/03 18:10:56, kalman wrote:
> > I don't think these actually need to be around still?
> 
> Yeah, I guess we should remove them if we don't need them. The fact that I
used
> aliasing for backwards compatability probably means they don't need to be
> present for API call args checking. 
> 

Yeah I think that was enough.

Even so I'll make sure these paths are tested.

https://codereview.chromium.org/11745015/diff/12001/chrome/test/data/extensio...
File chrome/test/data/extensions/api_test/stubs/content_script.js (right):

https://codereview.chromium.org/11745015/diff/12001/chrome/test/data/extensio...
chrome/test/data/extensions/api_test/stubs/content_script.js:82: path !=
"runtime.lastError" &&
On 2013/01/03 22:42:27, Antony Sargent wrote:
> Should you have just removed this line, since there is a duplicate check one
> line down?
> 

Actually I think I shouldn't have changed this at all, thanks for noticing.

[commit-bot: I haz the power, 2013-01-07 16:47:28]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/kalman@chromium.org/11745015/24007

[commit-bot: I haz the power, 2013-01-07 16:48:38]

Presubmit check for 11745015-24007 failed and returned exit status 1.


Running presubmit commit checks ...

** Presubmit Messages **
If this change has an associated bug, add BUG=[bug number].

** Presubmit Warnings **
License must match:
.*? Copyright (\(c\) )?(2013|2012|2011|2010|2009|2008|2007|2006|2006-2008) The
Chromium Authors\. All rights reserved\.\n.*? Use of this source code is
governed by a BSD-style license that can be\n.*? found in the LICENSE file\.(?:
\*/)?\n
Found a bad license header in these files:
 
chrome/common/extensions/docs/examples/api/infobars/sandwichbar/contentscript.js
\
  chrome/common/extensions/docs/examples/api/messaging/timer/page.js \
  chrome/common/extensions/docs/examples/extensions/benchmark/script.js \
 
chrome/common/extensions/docs/examples/extensions/email_this_page/content_script.js
\
  chrome/test/data/devtools/extensions/devtools_messaging/background.js \
  chrome/test/data/devtools/extensions/devtools_messaging/devtools.js \
  chrome/test/data/extensions/api_test/content_scripts/isolated_world1/c.js \
  chrome/test/data/extensions/api_test/content_scripts/isolated_world2/a.js \
  chrome/test/data/extensions/api_test/executescript/in_frame/script.js \
  chrome/test/data/extensions/api_test/tabs/connect/echo.js

** Presubmit ERRORS **
Missing LGTM from an OWNER for files in these directories:
    chrome/browser/resources/file_manager

Presubmit checks took 26.1s to calculate.

[commit-bot: I haz the power, 2013-01-07 17:47:05]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/kalman@chromium.org/11745015/17006

[commit-bot: I haz the power, 2013-01-07 20:05:13]

Retried try job too often on win_aura for step(s) interactive_ui_tests

[commit-bot: I haz the power, 2013-01-08 01:39:50]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/kalman@chromium.org/11745015/18232