Quote:
Originally Posted by jhowell
You can’t have bare text inside of the blockquote. Use something like:
<blockquote><p>Cras ornare massa odio.</p></blockquote> |
Quote:
Originally Posted by Vroni
to be honest i never used blockquote cause it doesnt make sense to me. I prefer divs as a container or adding classes to the paragrafs if needed.
|
As Turtle91 said, there are semantic reasons why you want to use the more specific <blockquote> instead of simple <div>.
Quote:
Originally Posted by Vroni
Blockquota just adds some indentation/margins/paddings around some other elements an d you never know what the target renderer will do with it.
|
No. It's
not "just indentation/margins", there's meaning behind marking it: a longer quote.
It's just like you marking <h1> for headings instead of <div class="heading">... it's not "just bigger bold font".
And if you follow standards, everyone is better off because of higher-level functionality.
Here's a few simple examples I could think of off the top of my head:
- Anything that overrides CSS, like Firefox's "Reader View", can have proper fallbacks.
- (I'm LOVING using Reader View on Mobile too, it makes reading those damn "Mobile-Optimized sites" so much better.)
- Conversion to different formats.
- Printing might adjust widows/orphans, so a quote doesn't get broken across pages.
- A Screen Reader can read long quotes with a slightly different tone.
- Text-to-Speech can add extra pause between blockquotes.
- Screen Readers can easily navigate the document by "jumping to the next blockquote".
Just like marking <h1-h6>, you can then easily generate TOCs, or have a floating TOC at the side.
Using standard tags allows much more robust handling across all types of use-cases (even many future ones).