Chromium Code Reviews| OLD | NEW |
|---|---|
| (Empty) | |
| 1 <p> | |
|
not at google - send to devlin
2015/02/13 17:27:32
Delete this file, but add a new one to articles/in
Devlin
2015/02/13 21:18:33
Done.
| |
| 2 The infobars API allows you to add a | |
| 3 horizontal panel just above a tab's contents, | |
| 4 as the following screenshot shows. | |
| 5 </p> | |
| 6 | |
| 7 <p> | |
| 8 <img src="{{static}}/images/infobar.png" | |
| 9 width="722" height="150" | |
| 10 alt="An infobar asking whether the user wants to translate the current page" / > | |
| 11 </p> | |
| 12 | |
| 13 <p> | |
| 14 Use an infobar to tell the reader | |
| 15 something about a particular page. | |
| 16 When the user leaves the page for which the infobar is displayed, | |
| 17 Google Chrome automatically closes the infobar. | |
| 18 </p> | |
| 19 | |
| 20 <p> | |
| 21 You implement the content of your | |
| 22 infobar using HTML. Because infobars are ordinary pages inside an extension, | |
| 23 they can | |
| 24 <a href="overview#pageComm">communicate with other extension pages</a>. | |
| 25 </p> | |
| 26 | |
| 27 | |
| 28 <h2 id="manifest">Manifest</h2> | |
| 29 | |
| 30 <p> | |
| 31 The infobars API is avaiable under "infobars" | |
| 32 permission and dev channel only. Also, you should specify | |
| 33 a 16x16-pixel icon for display next to your infobar. | |
| 34 For example: | |
| 35 </p> | |
| 36 | |
| 37 <pre data-filename="manifest.json"> | |
| 38 { | |
| 39 "name": "Andy's infobar extension", | |
| 40 "version": "1.0", | |
| 41 <b>"permissions": ["infobars"],</b> | |
| 42 <b>"icons": {</b> | |
| 43 <b>"16": "16.png"</b> | |
| 44 <b>},</b> | |
| 45 "background": { | |
| 46 "scripts": ["background.js"] | |
| 47 } | |
| 48 } | |
| 49 </pre> | |
| OLD | NEW |