| OLD | NEW |
|---|
| 1 <div id="pageData-title" class="pageData">NPAPI Plugins</div> | 1 <div id="pageData-name" class="pageData">NPAPI Plugins</div> |
| 2 | 2 |
| 3 <p> | 3 <p> |
| 4 Leveraging HTML and JavaScript | 4 Leveraging HTML and JavaScript |
| 5 makes developing new extensions really easy, | 5 makes developing new extensions really easy, |
| 6 but what if you have existing legacy or proprietary code | 6 but what if you have existing legacy or proprietary code |
| 7 that you want to reuse in your extension? | 7 that you want to reuse in your extension? |
| 8 You can bundle an NPAPI plugin with your extension, | 8 You can bundle an NPAPI plugin with your extension, |
| 9 allowing you to call into native binary code from JavaScript. | 9 allowing you to call into native binary code from JavaScript. |
| 10 </p> | 10 </p> |
| 11 | 11 |
| (...skipping 76 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 88 including an NPAPI plugin whenever possible. | 88 including an NPAPI plugin whenever possible. |
| 89 </p> | 89 </p> |
| 90 | 90 |
| 91 <p> | 91 <p> |
| 92 Marking your NPAPI plugin "public" increase the attack surface of your | 92 Marking your NPAPI plugin "public" increase the attack surface of your |
| 93 extension because the plugin is exposed directly to web content, making | 93 extension because the plugin is exposed directly to web content, making |
| 94 it easier for a malicious web site to manipulate your plugin. Instead, | 94 it easier for a malicious web site to manipulate your plugin. Instead, |
| 95 avoid making your NPAPI plugin public whenever possible. | 95 avoid making your NPAPI plugin public whenever possible. |
| 96 </p> | 96 </p> |
| 97 | 97 |
| OLD | NEW |
|---|
Chromium Code Reviews
Issue 465039:
Extension Doc Changes (no building or testable changes) (Closed)
