Index: chrome/common/extensions/docs/templates/articles/npapi.html |
diff --git a/chrome/common/extensions/docs/templates/articles/npapi.html b/chrome/common/extensions/docs/templates/articles/npapi.html |
index fa95439ed22d04cb460a127eac612f009c2a4028..9c21104a7c1ba1f20514cf4e3665d75032ecc803 100644 |
--- a/chrome/common/extensions/docs/templates/articles/npapi.html |
+++ b/chrome/common/extensions/docs/templates/articles/npapi.html |
@@ -11,6 +11,9 @@ allowing you to call into native binary code from JavaScript. |
<h2 id="warning">Warning</h2> |
+<p align="center"><b><a href="http://blog.chromium.org/2013/09/saying-goodbye-to-our-old-friend-npapi.html">NPAPI is being phased out.</a> |
+Consider using alternatives.</b></p> |
+ |
<p align="center"><b>NPAPI is a really big hammer that should only be used when no other approach will work.</b> |
<p>Code running in an NPAPI plugin has the full permissions of the current user and is not sandboxed or shielded from malicious input by Google Chrome in any way. You should be especially cautious when processing input from untrusted sources, such as when working with <a href="content_scripts.html#security-considerations">content scripts</a> or XMLHttpRequest. |