jason cook wrote:
Mozilla will do progressive rendering.OK. I take it this is default behavior, that doesn't require anything in the HTML other than a <table> tag, right?
Yes.
Pass 1 is basically done to find out what size each cell would _like_ to be. Pass 2 is done to actually size the cells. The issue is that each cell should be the size of its content (even if it has a width set; in such cases it should be the max of that width and the content width). So you have to find out how big the content inside is. When that content is a table, you have to reflow that table, and so forth.Makes sense. Any idea what happens in the first pass, vs. the second pass? I want to make sure I understand what you mean by 'shrink-wrap / auto-size'
http://lxr.mozilla.org/seamonkey/source/layout/doc/table_reflow_slides.html#s10 has some more information on table reflow....
Thanks, now that you pointed this out, I've been able to find a fair amount of documentation to back this up. Out of curiousity, what exactly happens when a fixed-width table is over-constrained in Mozilla?
Generally we aim for "lay it out like IE does"....
If the overconstraint is due to something in row N we would show the rows up to N and then reflow when we hit the new constraint.Does it display the incorrectly-sized table as it's working, and then redisplay it properly -- or does it re-render the table from square 1 before displaying anything to the scree?
I'll include this. BTW, what about HTTP1.1 support -- though it's not something that is enabled via HTML, it does seem like something folks could request of their sysadmin... is HTTP1.1 new in Mozilla / Nav6, or was it in the 4.x release, too?
It wasn't in 4.x
