Closed
Bug 267592
Opened 21 years ago
Closed 20 years ago
[FIX]table column background not right when using the overflow: auto;
Categories
(Core :: Layout: Tables, defect, P1)
Core
Layout: Tables
Tracking
()
RESOLVED
FIXED
mozilla1.8alpha6
People
(Reporter: impala, Assigned: bzbarsky)
References
()
Details
(Keywords: testcase)
Attachments
(4 files, 1 obsolete file)
388 bytes,
text/html
|
Details | |
822 bytes,
text/html
|
Details | |
902 bytes,
text/html
|
Details | |
8.40 KB,
patch
|
fantasai.bugs
:
review+
roc
:
superreview+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1
background colors given to colgroup elements are not drawn correctly when the
table contains more than one TBODY element (or contains both a THEAD and a TBODY
element); AND the TBODY element(s) has the CSS property overflow: auto;
SEE the the sample in the URL. This happens with the overflow: auto;
property/value pair set for the TBODY element(s).
This may be related to the fix for bug 4510
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Actual Results:
It appears to me that the background color for each child of TABLE is being
drawn from the top of TABLE, not from the top of each child. Thus they
overwrite each other, and do not fill out the table as expected.
Expected Results:
In my demonstration url, I expect the last table to look basically the same as
the middle table.
thanks for the test case :)
Assignee: nobody → fantasai.bugs
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: testcase
OS: Windows XP → All
Hardware: PC → All
Summary: table column background not right when using the overflow: auto; → table column background not right when using the overflow: auto;
![]() |
Assignee | |
Comment 2•21 years ago
|
||
![]() |
Assignee | |
Comment 3•21 years ago
|
||
![]() |
Assignee | |
Comment 4•21 years ago
|
||
![]() |
Assignee | |
Comment 5•21 years ago
|
||
Comment on attachment 164605 [details] [diff] [review]
Fix
When it's scrollable, the table row group is a kid of the scrollframe, not the
table frame. So the coordinate conversions have to be handled a little more
carefully...
Attachment #164605 -
Flags: superreview?(roc)
Attachment #164605 -
Flags: review?(fantasai.bugs)
![]() |
Assignee | |
Comment 6•21 years ago
|
||
Attachment #164605 -
Flags: superreview?(roc) → superreview+
Any reason why you're passing parameters for the offset instead of modifying the
calculation for rowgroups with views from within the row group function?
![]() |
Assignee | |
Comment 8•21 years ago
|
||
Because I need that offset in the "does the row group overlap the dirty rect?"
code in the table function... I suppose I could just call GetOffsetTo() twice,
but it's not _all_ that cheap, so I figured I'd avoid it.
Comment on attachment 164605 [details] [diff] [review]
Fix
Instead of passing the offset as a parameter, you should use the mRowGroup data
member. Set the offsets on its mRect in the calling function, then use a
SetData function (that sets what SetFull sets but doesn't touch the mRect)
instead of SetFull in the painting function.
Attachment #164605 -
Flags: review?(fantasai.bugs) → review-
![]() |
Assignee | |
Comment 10•21 years ago
|
||
Assignee: fantasai.bugs → bzbarsky
Attachment #164605 -
Attachment is obsolete: true
Status: NEW → ASSIGNED
![]() |
Assignee | |
Updated•21 years ago
|
Priority: -- → P1
Summary: table column background not right when using the overflow: auto; → [FIX]table column background not right when using the overflow: auto;
Target Milestone: --- → mozilla1.8alpha6
![]() |
Assignee | |
Updated•21 years ago
|
Attachment #166030 -
Flags: review?(fantasai.bugs)
Comment 11•21 years ago
|
||
Comment on attachment 166030 [details] [diff] [review]
Per comments
If you can slip
+ // Need to compute the right rect via GetOffsetTo, since the row
+ // group may not be a child of the table.
+ mRowGroup.mRect.MoveTo(rg->GetOffsetTo(aTableFrame));
under an 'if' statement so getOffset is only called when necessary, do that.
Other than that, r=fantasai :)
Attachment #166030 -
Flags: review?(fantasai.bugs) → review+
![]() |
Assignee | |
Comment 12•21 years ago
|
||
Comment on attachment 166030 [details] [diff] [review]
Per comments
I thinking checking whether to call it would cost about as much as calling
it...
Attachment #166030 -
Flags: superreview+
![]() |
Assignee | |
Comment 13•21 years ago
|
||
Comment on attachment 166030 [details] [diff] [review]
Per comments
er, requesting sr, not setting. ;)
Attachment #166030 -
Flags: superreview+ → superreview?(roc)
Attachment #166030 -
Flags: superreview?(roc) → superreview+
![]() |
Assignee | |
Comment 14•21 years ago
|
||
Fixed.
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Comment 15•20 years ago
|
||
The more comprehensive testcase draws below the table on initial load.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Perhaps that should be a separate bug?
Comment 17•20 years ago
|
||
I filed bug 317137 as the followup
Status: REOPENED → RESOLVED
Closed: 21 years ago → 20 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•