maxAscent/maxDescent not backed up

VERIFIED FIXED

Status

()

Core
Layout
P2
normal
VERIFIED FIXED
20 years ago
18 years ago

People

(Reporter: kipp, Assigned: buster)

Tracking

Trunk
x86
Windows NT
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

20 years ago
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.
(Reporter)

Updated

20 years ago
Status: NEW → ASSIGNED
(Reporter)

Comment 1

20 years ago
still need to do max-element-size
(Reporter)

Updated

19 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
(Reporter)

Comment 2

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

Comment 3

19 years ago
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

Updated

19 years ago
Status: RESOLVED → VERIFIED

Comment 4

19 years ago
marking verified for completeness sake
You need to log in before you can comment on or make changes to this bug.