Closed
Bug 47051
Opened 25 years ago
Closed 24 years ago
Second column is not correctly horizontally aligned
Categories
(Core :: Layout: Tables, defect, P3)
Tracking
()
mozilla1.0
People
(Reporter: Mitja.Perko, Assigned: attinasi)
References
()
Details
(Keywords: testcase)
Attachments
(2 files)
Second column should be aligned to top and not to bottom. See behaviour in
Netscape 4.7 as the correct behaviour.
Comment 2•25 years ago
|
||
justin@ice.kewlio.net makingtest
Comment 3•25 years ago
|
||
Comment 4•25 years ago
|
||
seems to me like this is just an example of a bad generator (frontpage 4.0).
Original Code:
<td WIDTH="6%" HEIGHT="16" bgcolor="#CCFFFF" valign="top"><font SIZE="2"><p
ALIGN="center"></font><strong><font face="Arial" size="2">poz</font></strong></td>
which is fixed when the pointless <font> tag is taken out, and the <p> tag is
closed. so the code would look like this:
<td WIDTH="6%" HEIGHT="16" bgcolor="#CCFFFF" valign="top"><p
ALIGN="center"><strong><font face="Arial" size="2">poz</font></strong></p></td>
sorry for flooding all your e-mails.
Comment 6•25 years ago
|
||
The 2nd and 3rd cell blocks in the 1st row are returning a larger desired
height, causing the row to be higher than Nav4.x. Reassigning to attinasi and
moving to m0.9.2.
Row 00CA9598 r=0 a=UC,UC c=UC,UC cnt=36
Cell 00CA95E0 r=0 a=UC,UC c=UC,UC cnt=37
Block 00CA963C r=0 a=UC,UC c=UC,UC cnt=38
Block 00CA963C d=300,285 me=300
Cell 00CA95E0 d=330,315 me=330
Cell 00CA96EC r=0 a=UC,UC c=UC,UC cnt=39
Block 00CA9748 r=0 a=UC,UC c=UC,UC cnt=40
Block 00CA9748 d=330,525 me=330
Cell 00CA96EC d=360,555 me=360
Cell 00CA98CC r=0 a=UC,UC c=UC,UC cnt=41
Block 00CA9928 r=0 a=UC,UC c=UC,UC cnt=42
Block 00CA9928 d=375,525 me=375
Cell 00CA98CC d=405,555 me=405
Row 00CA9598 d=UC,555
Assignee: karnaze → attinasi
Target Milestone: --- → mozilla0.9.2
| Assignee | ||
Comment 7•25 years ago
|
||
by mandate, moving non-crashers and non-datalossers outward.
Status: NEW → ASSIGNED
Target Milestone: mozilla0.9.2 → mozilla1.0
Comment 8•24 years ago
|
||
Snip from the testcase:
<td><font><p></font>1
will be parsed as:
<td><font></font><p>1</p>
which is why the quirk margin collapse for "td > :first-child" does not work.
This is really a dup of bug 33784 but leaving it to you Marc if you want to
keep them as separate issues.
| Assignee | ||
Comment 9•24 years ago
|
||
Thanks Mats - I'll dup them since I think your analysis is right-on. Also, I'll
attach a modification of the testcase with the <font> moved to after the <p> to
show that it all works when the the :first-child is the <p> and not the <font>
*** This bug has been marked as a duplicate of 33784 ***
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
| Assignee | ||
Comment 10•24 years ago
|
||
You need to log in
before you can comment on or make changes to this bug.
Description
•