Closed Bug 142368 Opened 22 years ago Closed 22 years ago

Absolutely positioned children in an absolutely positioned table have wrong containing block

Categories

(Core :: Layout: Tables, defect)

defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 63895

People

(Reporter: bora123, Assigned: karnaze)

Details

(Keywords: testcase)

Attachments

(1 file)

Absolutely positioned Child nodes in an absolutely positioned table must be 
placed relative to the parent node's coordinates, not relative to the client 
area's coordinates. For example, Let say that I want to place a table inside 
another table, both having absolute positions. Parent table is placed on 
left:100 top:100. If I want to place the second table as a child node inside 
the parent table at the coordinate top:10; left:10, the child table must be 
placed in fact onto top:110 left:110.
Here is a demonstration attached.
Confirmed.
Assignee: attinasi → karnaze
Status: UNCONFIRMED → NEW
Component: Layout → HTMLTables
Ever confirmed: true
Keywords: testcase
QA Contact: petersen → amar
Summary: Absolutely positioned Child nodes in an absolutely positioned table → Absolutely positioned children in an absolutely positioned table have wrong containing block
Where should the inner table is placed if the outer table has a caption?  That
is, would "top:0" mean "line up with the top of the caption" or "line up with
the top of the first row"?
OS: Windows ME → All
Hardware: PC → All
Both ways are acceptable. I would personally go with top:0. It would be best to 
hear others on this.

um... you did not answer my question, really....  The question was "What is
considered the containing block -- the box that includes the table and captions,
or the box that just includes the table?"
Sorry I should have been more descriptive, I think 

>"top:0" mean "line up with the top of the caption"

is the way to go.
please be aware that captions in abs. pos tables have a problem: bug 84715
Dupe of bug 63895 "relative/absolute positioned table not abs pos containing block"

*** This bug has been marked as a duplicate of 63895 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: