take look at it with this brwoser version and the 4.7 version regards, lenix
Verified on M13 Win95, but could be all platforms. NS4.7 and M13 cope with the situation where a <td> is width=100% and then there's another one in the same row, and that second <td> contains two graphics, differently. NS4.7 puts them together horizontally, M13 vertically. Testcase, boiled down from URL above, attached. It uses publically available (http://www.bbc.co.uk) graphics for simplicity. Note: if you insert a newline between the two <img> tags in the testcase, NS4.7 starts doing the same thing as Mozilla - i.e. arranging them vertically. Gerv
*** Bug 25668 has been marked as a duplicate of this bug. ***
Sorry about that - the first test case _had_ the abovementioned \n in it, and so appeared the same in both browsers. Verified still a problem in 2000021615 W95. Gerv
Having a % based cell determine the width of an auto width table is a "quirk" and violates the standard. IE gets around this in the 2nd attachment by ensuring that the adjacent images never wrap, which isn't necessarily the right thing to do. I'm not sure how to fix this in "quirks mode" because, I thought that the behavior was to let the 100% cell get as much width as it could. This test case disproves that theory.
I just ran into this same problem. I have an element that I want to take up 100% of the width EXCEPT for the space another cell is taking up. As you mentioned, IE has found a way around this problem. Here's my comments on the subject for what little it is worth :-) I agree with Mozilla's implementation, not IE's. A good way around this problem SHOULD be to insert extra TD tags. HOWEVER, it does not work correctly with BUTTON tags. In my opinion, this is the problem that needs to be addressed. Refer to the coming testcase where table cells overlap, and the orginal testcase is FIXED.
Rod, it looks like the button (3rd attachment) is reporting a max element width smaller than its desired width during the table's unconstrained reflow. When the table later reflows it with the max element width it spills into the next cell.
for got to set "fixed"
I guess I can't actually verify this since I didn't report it. Whatever, I agree that this is fixed.
Verified fixed. Nav and Netscape 6 display identically with 9/14 build.