Framesets, layers, and tables.
Straight_Man
Geeky, in my own wayNaples, FL Icrontian
IE, starting with IE5, has an odd behavior (no this does NOT go in Windows or software).
When you stick a table def inside a cell in a table it has started to parse, two things happen:
First, the cell maximum width is defined as the layer minimum for the tables in the cell, as it is layering the tables on top of what now is an underlying table. Yuo have three choices-- you can not define the width of cell you want to contain a table, in which case it will top down parse the overall table and then paint what you want according to the align for each td in the tr pair, left to right, or you do not put tbales in a cell and feed to IE. Third choice is to use framesets for IE and tables for mozilla as mozilla will use table def and override width of cell if need be unless table overall width is defined.
So, lets say you want one three column site without layering and without framesets.... You can leave the column width undefined, use graphics left and right which will force an implicit sizing of the left and right columns, and the middle column will be floatable widthwise, or you can define center column width and then use paragraph and divs within, and literally defined width image tags in paragraph tags or cells to force the overall column minimum width.
IE basicly does not like table on table layering. It prefers framesets for overall structure where you want a floating width page with variable content in each subarea. IE parses table on table layers top-down, inner table defs can override, and if something is not defined it can use the enclosing table defs, or even the enclosing CELL defs.
Mozilla parses whole table first, and can toss out conflicting things within the structure of table(s) enclosed in cell(s).
If you do not believe me, read and understand Danny Chapman's writings on HTML and other programming used for webdev(published by O'Reilly and Associates)-- his HTML book is a classic and lots of what he teaches still holds true today. Read with emphasis to understanding differences between IE and Mozilla\Netscape and note this has been grandfathered forward from IE 5.0(actually part of it was exhibited in IE 4.0) for the most part (SP3 for IE 4.0 also brought some of the diffs into play in IE 4.0, and SP2 for IE 4.0 also altered some behaviors of IE-- but the layering behavior of IE is left mostly intact clear through IE 6).
John.
When you stick a table def inside a cell in a table it has started to parse, two things happen:
First, the cell maximum width is defined as the layer minimum for the tables in the cell, as it is layering the tables on top of what now is an underlying table. Yuo have three choices-- you can not define the width of cell you want to contain a table, in which case it will top down parse the overall table and then paint what you want according to the align for each td in the tr pair, left to right, or you do not put tbales in a cell and feed to IE. Third choice is to use framesets for IE and tables for mozilla as mozilla will use table def and override width of cell if need be unless table overall width is defined.
So, lets say you want one three column site without layering and without framesets.... You can leave the column width undefined, use graphics left and right which will force an implicit sizing of the left and right columns, and the middle column will be floatable widthwise, or you can define center column width and then use paragraph and divs within, and literally defined width image tags in paragraph tags or cells to force the overall column minimum width.
IE basicly does not like table on table layering. It prefers framesets for overall structure where you want a floating width page with variable content in each subarea. IE parses table on table layers top-down, inner table defs can override, and if something is not defined it can use the enclosing table defs, or even the enclosing CELL defs.
Mozilla parses whole table first, and can toss out conflicting things within the structure of table(s) enclosed in cell(s).
If you do not believe me, read and understand Danny Chapman's writings on HTML and other programming used for webdev(published by O'Reilly and Associates)-- his HTML book is a classic and lots of what he teaches still holds true today. Read with emphasis to understanding differences between IE and Mozilla\Netscape and note this has been grandfathered forward from IE 5.0(actually part of it was exhibited in IE 4.0) for the most part (SP3 for IE 4.0 also brought some of the diffs into play in IE 4.0, and SP2 for IE 4.0 also altered some behaviors of IE-- but the layering behavior of IE is left mostly intact clear through IE 6).
John.
0
This discussion has been closed.
Comments
Do you live under a rock? Or are you friends with Mr Ageek? As if you follow his progress you will find that pretty much anything he says, is infact wrong. But you don't care about people screwing things up through being given wrong information now do you?