Closed
Bug 2822
Opened 26 years ago
Closed 26 years ago
<p> break not shown between </span> & <address>
Categories
(Core :: Layout, defect, P3)
Tracking
()
VERIFIED
FIXED
M4
People
(Reporter: rootrider, Assigned: rickg)
References
()
Details
Reference URL: http://members.xoom.com/rootrider/index.html
The paragraph break that's usually shown when <p> is inserted doesn't exist.
Near the bottom of the page (directly below the HR) is a row of three links
that are enclosed in the <span> element. Each link contains the class=
attribute. After <span> closes I have a <p> to indicate a new paragraph for the
<address> section of my page. But it isn't shown. The text contained in
<address> is "stylized" according to the external stylesheet (default.css).
Here are the properties for <address>:
ADDRESS {font-family: "Arial", "Verdana", sans-serif; font-size: 75%;
text-align: Left;}
---------------------
"Tacoma, WA, USA" is contained both within the stylized address element and
<span class="smallsans"></span>
-Joel D. Parker
Reporter | ||
Comment 1•26 years ago
|
||
Also, I'm viewing the site in the Developer Preview (Gecko) downloaded from
http://developer.netscape.com on 1/30/99.
-Joel D. Parker
this isn't a rendering bug. if something doesn't even exist on the page it's
related to layout or the parser. i have no idea which one is the culprit here.
The main problem I see with the latest build is that there's too much vertical
space before the "Copyright" text at the bottom. This simple HTML demonstrates
the problem:
<p>Joel D. Parker
<table width="100%" border="0" cellspacing="0" cellpadding="1">
<tr>
<td class="note" valign="top" rowspan="2">
Copyright © 1999
</tr>
</table>
For some reason the parser is kicking the table that contains the copyright
notice out of the P tag that preceeds it.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Updated•26 years ago
|
QA Contact: 4110
Updated•26 years ago
|
Status: RESOLVED → VERIFIED
Comment 7•26 years ago
|
||
Using 3/1 build, verified fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•