5114 - {compat} Spacing around <p>...</p><br><p>...</p>

Status: VERIFIED INVALID

(Core :: Layout, defect, P3)

Description

[ekrock's old account (dead)]

This is subtle, but if you compare the layout of this page within DR1 and
Seam 4/14 AppRunner (make the windows the same size and line up the blue
"jump! travel" ribbons at the top), you'll see that extra vertical blank space
has appeared between the end of the first paragraph ("your suggestions today!")
and the top of the nested table, which is the next visual element on the page.

With all the style settings, you'd have to use a ruler to be sure, but since
this is a change from longstanding behavior, we should confirm that it's correct
behavior. Here's the relevant markup section.  The extra whitespace is popping
up between the <P> and the nested <TABLE ... >.

-----

		<TD><P align="justify" ID=line>
Welcome  to our newsletter, a brief monthly update detailing current happenings
at the JUMP!Travel Web site. We love to travel and know that you do too, so we
take a moment every month to highlight favorite destinations that you may want
to visit. Do you have a favorite restaurant in Istanbul? A special place that's
not to be missed in Sydney? Share it with our community by sending in your
suggestions today!</P><BR><P>



<!-- BEGIN NESTED TABLE -->
<!--  BACKGROUND="images/hotel.gif" -->
<TABLE COL=2 BORDER="0" CELLPADDING="12" CELLSPACING="0" WIDTH="100%">
	<TR>

		<TD VALIGN="TOP">
		<DIV CLASS="headline" STYLE="text-transform: capitalize;
letter-spacing: .3em; background-color: rgb(0, 0, 102); word-spacing: .5em;
color: white; font-size: 14pt; padding: 3px; opacity: 0.65">&nbsp;what's
new?</DIV><P>

* TRAVEL STORE: We will be adding a travel store next month, where you can
purchase your favorite books, videos and cassettes. We'll list our favorites to
start with, but encourage you to let us know which one's you like best so we can
add them to the list.<P>

Comment 1

[kipp]

It's a compatability issue. This sequence:

<P>whatever</P><BR><P>

will do different things in nav4 vs mozilla5. We are doing the correct thing,
according to CSS.

Comment 2

[Hixie (not reading bugmail)]

Since the difference is really quite subtle, I would tend to suggest that this
bug be marked invalid.

We have plenty of spec compliance issues and much more serious compatability
browser issues to worry about...

Comment 3

[kipp]

Attachment: Simplified test case demonstrating the compatability issue

Comment 4

[Antti Näyhä]

Verifying the test case as definitive & as-simple-as-possible.
Also setting priority to trivial - I agree with Ian that this isn't
really a major issue.

Comment 5

[ekrock's old account (dead)]

OK, if we're doing the right thing by CSS, then this "bug" should really only be
"fixed" when running in Nav4-quirks-mode, yes?  And "fixing" this is a very low
priority--may be post-5.0 or never.

Comment 6

[leger]

Updating to default Layout Assignee...kipp no longer with us :-(

Comment 7

[troy]

Why are you re-reassing layout bugs? Do NOT touch layout bugs.

The bugs are assigned to Kipp so they can stay neatly organized until we have a
new owner for the block/inline code.

Comment 8

[Hixie (not reading bugmail)]

I'm marking this INVALID, since it really is a subtle difference, and we are
correct, and we have nicer fish to fry. If someone can find a top 100 which
actually messes up because of this error then reopen it, but otherwise I
suggest we leave it closed.

Comment 9

[Chris Petersen]

Marking as verified invalid.