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

Side by Side Diff: chrome/common/extensions/docs/templates/intros/notifications.html

Issue 12996003: Dynamically generate a heading for Extension Docs API pages (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Minor changes Created 7 years, 7 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 unified diff | Download patch
OLDNEW
1 <table class="intro">
2 <tr>
3 <th scope="col"></th>
4 <th scope="col"></th>
5 </tr>
6 <tr>
7 <td><strong>Description:</strong></td>
8 <td>Use the <code>chrome.notifications</code> module
9 to create rich notifications using templates and
10 show these notifications to users in the system tray
11 (see <a href="#usage">Usage</a>).</td>
12 </tr>
13 <tr>
14 <td><strong>Availability:</strong></td>
15 <td>Google Chrome Dev Channel Only</td>
16 </tr>
17 <tr>
18 <td><strong>Permissions:</strong></td>
19 <td><code>"notifications"</code></td>
20 </tr>
21 <tr>
22 <td><strong>Learn more:</strong></td>
23 <td><a href="https://developers.google.com/live/shows/83992232-1001/">Chrome Apps Office Hours: Rich Notifications</a></td>
24 </tr>
25 </table>
26
27 <p class="warning"> 1 <p class="warning">
28 <b>Warning: </b> 2 <b>Warning: </b>
29 Currently this API only works on ChromeOS and Windows. 3 Currently this API only works on ChromeOS and Windows.
30 </p> 4 </p>
31 5
32 <h2 id="usage">Usage</h2> 6 <h2 id="usage">Usage</h2>
33 7
34 <p> 8 <p>
35 To use this API, 9 To use this API,
36 call the $ref:notifications.create method, 10 call the $ref:notifications.create method,
(...skipping 74 matching lines...) Expand 10 before | Expand all | Expand 10 after
111 which respond to user actions. 85 which respond to user actions.
112 For example, 86 For example,
113 you can write an event handler to respond to an 87 you can write an event handler to respond to an
114 $ref:notifications.onButtonClicked event. 88 $ref:notifications.onButtonClicked event.
115 </p> 89 </p>
116 90
117 <p>Consider including event listeners and handlers within the 91 <p>Consider including event listeners and handlers within the
118 <a href="app_lifecycle.html#create_event_page">event page</a>, 92 <a href="app_lifecycle.html#create_event_page">event page</a>,
119 so that notifications can pop-up even when the app or extension isn't running. 93 so that notifications can pop-up even when the app or extension isn't running.
120 </p> 94 </p>
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698