Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 0 additions & 17 deletions source
Original file line number Diff line number Diff line change
Expand Up @@ -25091,23 +25091,6 @@ brighter. A &lt;b>rat&lt;/b> scurries past the corner wall.&lt;/p></code></pre>
style of a particular use is to be changed at a later date, the author doesn't have to go through
annotating each use.</p>

<p>The <code>b</code> element should be used as a last resort when no other element is more
appropriate. In particular, headings should use the <code>h1</code> to <code>h6</code> elements,
stress emphasis should use the <code>em</code> element, importance should be denoted with the
<code>strong</code> element, and text marked or highlighted should use the <code>mark</code>
element.</p>

<div class="example">

<p>The following would be <em>incorrect</em> usage:</p>

<pre class="bad"><code class="html">&lt;p>&lt;b>WARNING!&lt;/b> Do not frob the barbinator!&lt;/p></code></pre>

<p>In the previous example, the correct element to use would have been <code>strong</code>, not
<code>b</code>.</p>

</div>

<p class="note">Style sheets can be used to format <code>b</code> elements, just like any other
element can be restyled. Thus, it is not the case that content in <code>b</code> elements will
necessarily be boldened.</p>
Expand Down