Darin McGrew <mc****@stanfordalumni.orgwrote:
>>>But there are a few legitimate uses for using <br>, one example would be
to create a line break inside an <addresselement:
<address>
My name<br>
My address
<address>
Timothy Larson <th*********@cox.netwrote:
>>In these cases, I'd rather see a container element that enclosed each
line. Then you'd be able to style each line individually, which could
be useful.
Spartanicus <in*****@invalid.invalidwrote:
>Presentational markup such as <bor <ican be used, or styled <span>s,
but you'd still need the <br>.
If HTML included a <line>...</linemarkup, you wouldn't need <br>:
<address>
<line>John Doe</line>
<line>123 Main Street</line>
<line>Anytown USA</line>
</address>
<stanza>
<couplet>
<line>Roses are red</line>
<line>Violets are blue</line>
</couplet>
<couplet>
<line>If it's good enough for Tim</line>
<line>Then it's good enough for you</line>
</couplet>
</stanza>
Sure, you can work around it by using <div>, or a combination of <brand
<span>, but <line>...</lineor something similiar would have been nice.
Assuming you'd want to retain validity and the semantics of the
<addresselement, then using <divinside the element is not an option.
(For the sake of not drifting to far off of what is being discussed I'm
ignoring the ambivalence of the element's semantics)
I'd agree that there is a need for an HTML element that could for
example be used for marking up lines of poetry or a lyric, or indeed the
lines inside an <addresselement. For the latter case the <address>
element would have to be changed to allow block level child elements,
assuming that the new element would be of type "block".
Using <div>s to mark up things like lines of poetry is something of an
anomaly, semantically
<div>Roses are red</div>
<div>Violets are blue</div>
equates to "Rose are red Violets are blue", which obviously is a problem
in certain rendering situations.
--
Spartanicus
