L. David Baron wrote:
Although, given the two extra parameters this code passes to the reflow state constructor, does this even matter?
Without that change, exercising this code leads to: 175 NS_ASSERTION(availableWidth != NS_UNCONSTRAINEDSIZE, 176 "shouldn't use unconstrained widths anymore"); being hit at the top of nsHTMLReflowState::Init. I think that assert is correct.... -Boris _______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
