docs for chrome.devtools.panels & inspectedWindow

docs for chrome.devtools.panels & inspectedWindow

I'm refiling the CL from https://codereview.chromium.org/283603003/ on behalf of mem.

BUG=

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

[paulirish, 2014-07-16 03:01:21]

The LGTM'd patch from https://codereview.chromium.org/283603003/#msg11 now
addresses those two nits.

[caseq, 2014-07-16 06:12:06]

lgtm with a nit.

https://chromiumcodereview.appspot.com/391243004/diff/1/chrome/common/extensi...
File chrome/common/extensions/api/devtools/inspected_window.json (right):

https://chromiumcodereview.appspot.com/391243004/diff/1/chrome/common/extensi...
chrome/common/extensions/api/devtools/inspected_window.json:91: "description":
"Evaluates a JavaScript expression in the context of the main frame of the
inspected page. The expression must evaluate to a JSON-compliant object,
otherwise an exception is thrown. The eval function can report either a
DevTools-side error or a JavaScript exception that occurs during evaluation. In
either case, the <code>result</code> parameter of the callback is
<code>undefined</code>. In the case of a DevTools-side error, the
<code>isException</code> parameter is non-null and has <code>isError</code> set
to true and <code>code</code> set to an error code. In the case of a JavaScript
error, <code>isException</code> is set to true and <code>result</code> is set to
the string value of thrown object.",
Just noticed contradicting statements here: 
1) In either case, the <code>result</code> parameter of the callback is
<code>undefined</code>

2) In the case of a JavaScript error, <code>isException</code> is set to true
and <code>result</code> 

(in reality, the former is correct and it's the "value" field of exception
parameter that is set to the string value of thrown object)

[paulirish, 2014-07-16 06:50:47]

The CQ bit was checked by paulirish@chromium.org

[commit-bot: I haz the power, 2014-07-16 06:53:13]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/paulirish@chromium.org/391243004/20001

[commit-bot: I haz the power, 2014-07-16 11:17:17]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  chromium_presubmit on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/chromium_presubmit/bu...)
  win_chromium_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_rel/buil...)

[commit-bot: I haz the power, 2014-07-16 11:21:17]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-07-16 11:21:18]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/chromium_presubmit/bu...)

[paulirish, 2014-07-17 10:24:32]

The CQ bit was checked by paulirish@chromium.org

[commit-bot: I haz the power, 2014-07-17 10:25:36]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/paulirish@chromium.org/391243004/40001

[commit-bot: I haz the power, 2014-07-17 16:30:53]

Change committed as 283792