Closed Bug 245434 Opened 18 years ago Closed 18 years ago

text is hidden when nested tables are used


(Core :: Layout: Tables, defect)

Not set





(Reporter: spam, Assigned: bernd_mozilla)




(Keywords: testcase)


(4 files)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040514 MultiZilla/
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040514 MultiZilla/

The following HTML is viewable in mozilla 1.6 and IE, but not 1.7rc2

<TABLE height=100%>
		<td valign=top>
			<TABLE width=100% height=100%>

			<table width="768">


Reproducible: Always
Steps to Reproduce:
1. Put code shown above into html file and view in mozilla
2. or visit

Actual Results:  
in mozilla 1.7 you get a blank screen.. if you use the search feature you can
see that the text "test" is on the page but hidden under another table.

Expected Results:  
In IE and older versions of mozilla, and firefox you get a blank page with just
test at the top of the screen.
Oh, as a further note this was discovered as people using ModernBill are unable
to see client info as the table structure is a more complex version of the
example code.

For modernbill users here is a thread talking about the problem:

(sorry its passworded for only modernbill users)
Well, if you add properly the <tr><td></td></tr> tags in the first table, you
don't get to see any text inside any of the browsers (IE, Opera and Mozilla).
I think the other two browsers are doing something different (not good) when
they only see <table></table>.

I've attached reporter's testcase, but with 1px red borders.

See first paragraph of this:

I think this describes the testcase. It seems like user agents may do what they
like in this case.
Well, I would like it more when Mozilla provided a scrolling mechanism in this
case, or even better imho, when the containing table would grow to the
combining height of the two nested tables.
Empty tables don't have a size in other browsers (and in old Mozilla versions).
 Which is pretty incorrect...

We may add a quirk for this
Depends on: 240148
To be honest, I think the current behaviour is fine.  I believe IE has got this
wrong, as the only other interpretation that seems reasonable to me is for the
second inner table to push out below the 100% height boundary, i.e. causing the
window to scroll.  But then the outer table would exceed 100% ...

As CSS 2.1 remains quiet (aka "undefined") on this particular scenario, I
suggest keeping the current behaviour until the standard actually has something
to say on the matter, then we align with the standard.
Ever confirmed: true
Keywords: testcase
No longer depends on: 240148
Attached file Testcase #2
-> Tables
Assignee: parser → nobody
Component: HTML: Parser → Layout: Tables
OS: Windows XP → All
QA Contact: core.layout.tables
Depends on: 114430
*** Bug 261724 has been marked as a duplicate of this bug. ***
Attached patch patchSplinter Review
Assignee: nobody → bernd_mozilla
Attached patch patchSplinter Review
Blocks: 202078
Comment on attachment 160672 [details] [diff] [review]

David, I would like to enable showing the clipped overflow in strict mode to
see whether we can remove this alltogether. IE differs in this situation also
between quirks and standards mode.
Attachment #160672 - Flags: superreview?(dbaron)
Attachment #160672 - Flags: review?(dbaron)
Comment on attachment 160672 [details] [diff] [review]

It might be a little more logical (especially given the name of
HasPctOverHeight) to do the quirks mode check at the getter rather than the
setter (i.e., check in nsTableCellFrame::Paint, by adding an &&
eCompatibility_NavQuirks==compatMode with appropriate parentheses).  But either
way is ok with me.
Attachment #160672 - Flags: superreview?(dbaron)
Attachment #160672 - Flags: superreview+
Attachment #160672 - Flags: review?(dbaron)
Attachment #160672 - Flags: review+
The text will be hidden in quirks mode that is similiar to IE, in standards mode
we show the text, but do not expand the table (which IE does, but thats incorrect)
Closed: 18 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.