Extensions docs, declarativeWebRequest: notice being on hold

Extensions docs, declarativeWebRequest: notice being on hold

Because Declarative Web Request lacks an active owner at the moment, this CL adds a warning notice to the API's documentation site:
"this API is currently on hold, without concrete plans to move to stable"

Staged at https://chrome-apps-doc.appspot.com/_patch/276483005/extensions/declarativeWebRequest, but http://crbug.com/371402. Screenshots in my GDrive: https://drive.google.com/a/google.com/folderview?id=0Bx9cneu-k1RNeUZnRk5NWERObE0&usp=sharing (Google only, but let me know if you come from outside and need them).

Original at https://developer.chrome.com/extensions/declarativeWebRequest

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

[vabr (Chromium), 2014-05-08 16:40:02]

Hi Dominic,

Is this what you had in mind?

(Will send you screenshots in a separate e-mail, for reasons described in the
CL.)

Cheers,
Vaclav

[vabr (Chromium), 2014-05-08 16:47:44]

Actually managed to share the screenshots through Chrome OS Files app:
https://drive.google.com/a/google.com/folderview?id=0Bx9cneu-k1RNeUZnRk5NWERO...

[battre, 2014-05-09 09:18:20]

LGTM

https://codereview.chromium.org/276483005/diff/1/chrome/common/extensions/api...
File chrome/common/extensions/api/declarative_web_request.json (right):

https://codereview.chromium.org/276483005/diff/1/chrome/common/extensions/api...
chrome/common/extensions/api/declarative_web_request.json:8: "description":
"<em>Note: this API is currently on hold, without concrete plans to move to
stable.</em> Use the <code>chrome.declarativeWebRequest</code> API to intercept,
block, or modify requests in-flight. It is significantly faster than the <a
href='webRequest.html'><code>chrome.webRequest</code> API</a> because you can
register rules that are evaluated in the browser rather than the JavaScript
engine with reduces roundtrip latencies and allows higher efficiency.",
How about adding a <b></b> around "Note:" in addition?

[vabr (Chromium), 2014-05-09 10:34:42]

Thanks, Dominic. Comment addressed and screenshots updated.

Mike, Could you please add an OWNERS approval?

Cheers,
Vaclav

[Mike West, 2014-05-09 10:45:30]

LGTM with one comment.

https://codereview.chromium.org/276483005/diff/20001/chrome/common/extensions...
File chrome/common/extensions/api/declarative_web_request.json (right):

https://codereview.chromium.org/276483005/diff/20001/chrome/common/extensions...
chrome/common/extensions/api/declarative_web_request.json:8: "description":
"<em><b>Note:</b> this API is currently on hold, without concrete plans to move
to stable.</em> Use the <code>chrome.declarativeWebRequest</code> API to
intercept, block, or modify requests in-flight. It is significantly faster than
the <a href='webRequest.html'><code>chrome.webRequest</code> API</a> because you
can register rules that are evaluated in the browser rather than the JavaScript
engine with reduces roundtrip latencies and allows higher efficiency.",
Don't use <b>. Use <strong>.

[vabr (Chromium), 2014-05-09 11:42:30]

Thanks, Mike!
Comment addressed, sending to the CQ.
(I'm not going to complain about the red tree, as I'm the next sheriff, on
Monday and Tuesday. :))

Cheers,
Vaclav

https://codereview.chromium.org/276483005/diff/20001/chrome/common/extensions...
File chrome/common/extensions/api/declarative_web_request.json (right):

https://codereview.chromium.org/276483005/diff/20001/chrome/common/extensions...
chrome/common/extensions/api/declarative_web_request.json:8: "description":
"<em><b>Note:</b> this API is currently on hold, without concrete plans to move
to stable.</em> Use the <code>chrome.declarativeWebRequest</code> API to
intercept, block, or modify requests in-flight. It is significantly faster than
the <a href='webRequest.html'><code>chrome.webRequest</code> API</a> because you
can register rules that are evaluated in the browser rather than the JavaScript
engine with reduces roundtrip latencies and allows higher efficiency.",
On 2014/05/09 10:45:30, Mike West wrote:
> Don't use <b>. Use <strong>.

Done.

[vabr (Chromium), 2014-05-09 11:42:35]

The CQ bit was checked by vabr@chromium.org

[commit-bot: I haz the power, 2014-05-09 11:45:05]

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

[commit-bot: I haz the power, 2014-05-10 11:57:54]

Change committed as 269567