The second br tag within td class is ignored

[Jaxon Bridge]

This is really weird, and is a problem only on IE 6 for me, but not
Firefox.

Here is the code:

<td colspan=3 class=allmessagesheader>Pictures from
Europe<br><br><br>December 10, 2000</td>

Looks pretty basic, right? Well, the second <br> tag in there is
ignored. If I have only one <br> tag, it behaves as usual. The second
<br> tag does nothing, and if I add the third <br> tag, it behaves like
there are two, skipping a line of blank space (which is what I want).
Really weird. If I remove the class call, it works fine, and if I use
a different class, it works fine. So, must be the class. What does
the class have to say?

td.allmessagesheader {
color: #ffffff;
background-color: #003366;
font: 100% verdana, arial, sans-serif;
font-size: 16px;
line-height: 18px;
letter-spacing: 0.2em;
text-align: center;
}
So what in this code is causing <br> tags to not do their stuff?

I'm having the same exact problem with this code and class:

<table width=500><tr><td class=commententry>
<font class=ajstyle>
This is a list of all the posted messages for all pictures in all
galleries.
To jump to a particular photo, just click on it.
</font><br><br><br><font class=ajstyle>
Note that only photos with live comments are shown on this page.
</font>
</td></tr></table>

I have to escape the font class "ajstyle" before the <br> tags in order
for them *all* to be interpreted. The ajstyle class is:

font.ajstyle {
font: 90% verdana, arial, sans-serif;
letter-spacing: 0.2em;
color: #BEF5F3;
}

This is really weird.

I wish the world used Firefox.

Help appreciated.
Jaxon

[C A Upsdell]

Jaxon Bridge wrote:

This is really weird, and is a problem only on IE 6 for me, but not
Firefox.

Here is the code:

<td colspan=3 class=allmessagesheader>Pictures from
Europe<br><br><br>December 10, 2000</td>

Use <br>&nbsp;<br>&nbsp;<br>December 10, 2000

[Johannes Koch]

C A Upsdell > wrote:

Jaxon Bridge wrote:

<td colspan=3 class=allmessagesheader>Pictures from
Europe<br><br><br>December 10, 2000</td>

Use <br>&nbsp;<br>&nbsp;<br>December 10, 2000

The OP asked in a stylesheets news group. Why not tell him about margin
or padding?
--
Johannes Koch
In te domine speravi; non confundar in aeternum.
(Te Deum, 4th cent.)

[C A Upsdell]

Johannes Koch wrote:

C A Upsdell > wrote:

Jaxon Bridge wrote:

<td colspan=3 class=allmessagesheader>Pictures from
Europe<br><br><br>December 10, 2000</td>

Use <br>&nbsp;<br>&nbsp;<br>December 10, 2000

The OP asked in a stylesheets news group. Why not tell him about margin
or padding?

The OP's specific problem is not a CSS problem.

[Alan J. Flavell]

On Tue, 19 Jul 2005, C A Upsdell and MISSINGcupsdellXXX"TERMINATOR wrote:

Johannes Koch wrote:

C A Upsdell > wrote:

Use <br>&nbsp;<br>&nbsp;<br>December 10, 2000

The OP asked in a stylesheets news group. Why not tell him about margin or
padding?

The OP's specific problem is not a CSS problem.

So recommend solving it by taking away the original problem. If
there's still a genuine issue, apply a genuine solution, which the
original clutter was not. (Hint: there is no defined correct
behaviour for multiple <br> tags). (Hint: presentation detail belongs
in the stylesheet).

Heaping yet more clutter onto clutter that shouldn't have been there
in the first place is no solution (as well as being off-topic for the
stylesheets group, as was already remarked).

[Jaxon Bridge]

This worked, thanks, although I am curious why it was necessary to add
the non-binding space when working with classes, whereas outside of
classes the multiple <br> tags have always worked fine for me by
themselves.

You are right (the other poster) that I could probably solve the issue
using margin and padding options instead; I am new to CSS so old habits
die hard.

J

[C A Upsdell]

Alan J. Flavell wrote:

On Tue, 19 Jul 2005, C A Upsdell and MISSINGcupsdellXXX"TERMINATOR wrote:

Johannes Koch wrote:

C A Upsdell > wrote:

Use <br>&nbsp;<br>&nbsp;<br>December 10, 2000

The OP asked in a stylesheets news group. Why not tell him about margin or
padding?

The OP's specific problem is not a CSS problem.

So recommend solving it by taking away the original problem. If
there's still a genuine issue, apply a genuine solution, which the
original clutter was not. (Hint: there is no defined correct
behaviour for multiple <br> tags). (Hint: presentation detail belongs
in the stylesheet).

Heaping yet more clutter onto clutter that shouldn't have been there
in the first place is no solution (as well as being off-topic for the
stylesheets group, as was already remarked).

Sigh. I really did not want to get into this issue. Yes, I could have
provided a CSS solution, but there are cases when the <br> solution is
better, e.g. cases in which the XHTML 2.0 <l> tag would be appropriate,
and in any case it seemed to me that the OP was primarily concerned with
why their <br> solution was failing.

And yes, this is a CSS newsgroup, but if it is appropriate to suggest a
CSS solution in an HTML newsgroup (which happens all the time), then
surely it is _sometimes_ appropriate to suggest a relevant HTML solution
in a CSS newsgroup.

[kchayka]

C A Upsdell > wrote:

Jaxon Bridge wrote:

<td colspan=3 class=allmessagesheader>Pictures from
Europe<br><br><br>December 10, 2000</td>

Use <br>&nbsp;<br>&nbsp;<br>December 10, 2000

Seems to me a better solution would be to use semantic markup, like:

<h2>Pictures from Europe</h2>

and style h2 (or whatever) with desireable margin/padding values. Much
better than the kludgy <br> and non-breaking spaces, IMO.

--
Reply email address is a bottomless spam bucket.
Please reply to the group so everyone can share.

[Alan J. Flavell]

On Tue, 19 Jul 2005, C A Upsdell wrote:

Sigh. I really did not want to get into this issue.
Welcome to usenet...
Yes, I could have provided a CSS solution, but there are cases when the
<br> solution is better, e.g. cases in which the XHTML 2.0 <l> tag would
be appropriate,
I don't understand why you dragged in that extraneous detail. Kindly
review the subject header again. The topic is not a single <br> tag, but
multiple. I say again, there is no defined correct behaviour for multiple
<br> tags. "the second br tag...is ignored" is a perfectly valid
interpretation, and several browsers have taken this approach: once the
line has been broken, it's broken, and that's that.
and in any case it seemed to me that the OP was primarily concerned with
why their <br> solution was failing.
Correction: "multiple <br>".

But it's not "failing", since there's no defined correct behaviour.
And yes, this is a CSS newsgroup, but if it is appropriate to suggest a
CSS solution in an HTML newsgroup (which happens all the time), then
surely it is _sometimes_ appropriate to suggest a relevant HTML solution
in a CSS newsgroup.

Presentation is a stylesheet issue. If you can produce some reason that
the semantic structure of your content in HTML would need multiple <br>
tags, then I'd be quite surprised. I see no indication of it here, at any
rate. Even less after you've added your clutter to it.

have fun

[C A Upsdell]

Alan J. Flavell wrote:

Yes, I could have provided a CSS solution, but there are cases when the
<br> solution is better, e.g. cases in which the XHTML 2.0 <l> tag would
be appropriate,
I don't understand why you dragged in that extraneous detail. Kindly
review the subject header again. The topic is not a single <br> tag, but
multiple. I say again, there is no defined correct behaviour for multiple
<br> tags.

Sigh. There is no defined behaviour, but there is the behaviour that
the OP wanted, and my solution reliably gives them what they wanted.
Presentation is a stylesheet issue. If you can produce some reason that
the semantic structure of your content in HTML would need multiple <br>
tags, then I'd be quite surprised.

Whether there is some reason should be an issue for the OP, not for me,
and I am not going to second-guess the OP.