when a frame on a line ends up being pushed to the next line we don't backout that frames impact on: maxAscent maxDescent max-element-size etc. Start using the PerFrameData in nsInlineReflow and this can be easily fixed: change the code to compute the max values upon completion instead of on the fly.

still need to do max-element-size

max-element-size is only updated after a frame is placed, therefore there is no issue regarding backing it up.

still waiting for kipp@netscape.com to do 1 of the following: 1) provide QA with a test case so we can mark it VERIFIED_FIXED 2) verify it himself and mark this bug VERIFIED-FIXED

marking verified for completeness sake