Closed
Bug 73321
Opened 24 years ago
Closed 24 years ago
Data is truncated within a middle column where a colspan is used
Categories
(Core :: Layout: Tables, defect)
Tracking
()
VERIFIED
FIXED
mozilla0.9
People
(Reporter: garrett, Assigned: karnaze)
References
()
Details
(Keywords: regression)
Attachments
(2 files)
(deleted),
text/html
|
Details | |
(deleted),
patch
|
Details | Diff | Splinter Review |
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.2 i686; en-US; 0.8.1) Gecko/20010320
BuildID: 2001032105
Content is lost in the main column of a table where a colspan is used.
Reproducible: Always
Steps to Reproduce:
1.Visit the site; content is lost (mostly the poll, sometimes tuneup -- depends
on browser width)
Actual Results: Content is not displayed properly
Expected Results: Mozilla should have shown the complete tuneup area and all of
the poll as well
2001032021 - 2001-03-20 22:38 -- works fine
2001032105 - 2001-03-21 07:06 -- does not work (and also every build since)
Reporter | ||
Comment 1•24 years ago
|
||
Comment 2•24 years ago
|
||
Confirming, adding regression keyword and fixing url. Adding bernd who checked
in around this time.
I backed out my patch for bug 42187 and the testcase remained broken. There have
been two other checkins related to tables,
karnaze bug 23714 remove redundant style context resolution for table rows
timeless bug 70989
And this is more a table row problem, giving the hot potato back
Assignee: bernd.mielke → karnaze
Status: ASSIGNED → NEW
Assignee | ||
Updated•24 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9
Assignee | ||
Comment 5•24 years ago
|
||
Moving to m0.9
Assignee | ||
Comment 6•24 years ago
|
||
Assignee | ||
Comment 7•24 years ago
|
||
This bug was caused by the patch in bug 70989. Bernd, thanks for isolating
the checkins. The patch is checked in.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Comment 8•24 years ago
|
||
Verified fixed, nice turnaround time on this one :)
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•