Closed Bug 1571118 Opened 5 years ago Closed 5 years ago

Keep NS_FRAME_FIRST_REFLOW bit in nsBlockFrame::Reflow() a bit longer

Categories

(Core :: Layout, task, P5)

task

Tracking

()

RESOLVED FIXED
mozilla70
Tracking Status
firefox70 --- fixed

People

(Reporter: TYLin, Assigned: TYLin)

Details

Attachments

(1 file)

I notice that NS_FRAME_FIRST_REFLOW is cleared in the middle of nsBlockFrame::Reflow while developing a patch in https://phabricator.services.mozilla.com/D40245.

Although in the end the patch didn't require the bit to live for the full duration of nsBlockFrame's first reflow, I feel it might be better to keep the bit until nsFrame::DidReflow removes it in case anyone wants to add code to inspect it in the future.

This patch lets nsBlockFrame keep its NS_FRAME_FIRST_REFLOW bit a bit
longer, for the full duration of its first reflow, so that in the future
we may add more code to inspect it if needed before nsFrame::DidReflow()
clears it.

Pushed by aethanyc@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/3c48170ebbe2
Keep NS_FRAME_FIRST_REFLOW bit in nsBlockFrame::Reflow() until nsFrame::DidReflow(). r=dholbert
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla70
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: