Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(9186)

Unified Diff: chrome/common/extensions/docs/templates/articles/npapi.html

Issue 11035015: Merge 159156 - Extensions Docs Server: Fix headings with no IDs (Closed) Base URL: svn://svn.chromium.org/chrome/branches/1229/src/
Patch Set: Created 8 years, 3 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: chrome/common/extensions/docs/templates/articles/npapi.html
===================================================================
--- chrome/common/extensions/docs/templates/articles/npapi.html (revision 159603)
+++ chrome/common/extensions/docs/templates/articles/npapi.html (working copy)
@@ -9,7 +9,7 @@
allowing you to call into native binary code from JavaScript.
</p>
-<h2>Warning</h2>
+<h2 id="warning">Warning</h2>
<p align="center"><b>NPAPI is a really big hammer that should only be used when no other approach will work.</b>
@@ -18,7 +18,7 @@
<p>Because of the additional security risks NPAPI poses to users, extensions that use it will require manual review before being accepted in the
<a href="https://chrome.google.com/webstore">Chrome Web Store</a>.</p>
-<h2>Details</h2>
+<h2 id="details">Details</h2>
<p>
How to develop an NPAPI plugin is outside the scope of this document.
@@ -94,4 +94,4 @@
extension because the plugin is exposed directly to web content, making
it easier for a malicious web site to manipulate your plugin. Instead,
avoid making your NPAPI plugin public whenever possible.
-</p>
+</p>

Powered by Google App Engine
This is Rietveld 408576698