Lines Matching full:strong
17 <h4 id="New"><strong>New in L</strong></h4>
47 <li> The notification's <strong>icon</strong>, symbolizing the originating app, and also
50 <li> A notification <strong>title</strong> and additional <strong>text</strong></li>
51 <li> A <strong>timestamp</strong></li>
140 <p><strong>Notifications that should be bridged</strong></p>
149 <p><strong>Don't bridge</strong></p>
160 <p><strong>Actions to bridge</strong></p>
166 <p><strong>Actions not to bridge</strong></p>
257 <p><strong>Priority</strong></p>
260 <p><strong>Use</strong></p>
314 <h4 id="how_to_choose_an_appropriate_priority"><strong>How to choose an appropriate
315 priority</strong></h4>
475 <p><strong>Don't</strong></p>
481 <p><strong>Do</strong></p>
514 <div><p><strong>Do</strong></p>
518 <p><strong>Do</strong></p>
525 <p ><strong>Do</strong></p>
529 <p style="clear:both"><strong>Don't</strong></p>
569 <p>Notifications should be used primarily for <strong>time sensitive events</strong>, and especially
570 if these synchronous events <strong>involve other people</strong>. For instance, an incoming chat
706 <li> <strong>Example: </strong>An SMS app whose notifications include the text of the SMS and the sender's name and contact icon. This notification should be <code>VISIBILITY_PRIVATE</code>, but the <code>publicVersion</code> could still contain useful information like "3 new messages" without any other identifying details.
