Closed
Bug 789592
Opened 12 years ago
Closed 12 years ago
rename nsChangeHint_ReflowFrame and use it less
Categories
(Core :: CSS Parsing and Computation, defect)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
FIXED
mozilla18
People
(Reporter: dbaron, Assigned: dbaron)
Details
Attachments
(2 files)
3.44 KB,
patch
|
bzbarsky
:
review+
|
Details | Diff | Splinter Review |
19.06 KB,
patch
|
bzbarsky
:
review+
|
Details | Diff | Splinter Review |
I always have trouble remembering which of the reflow-related nsChangeHint_* values is the one that's the bitmask containing all the others. (Answer: nsChangeHint_ReflowFrame.) I'd like to rename this to nsChangeHint_AllReflowHints so it's clearer which one it is. I also think we can use it a bit less; there are a few places using it that are probably dating back to when it was a single bit, and should really be looking at one of the single bits. Patches coming shortly.
Assignee | ||
Comment 1•12 years ago
|
||
Attachment #659356 -
Flags: review?(bzbarsky)
Assignee | ||
Comment 2•12 years ago
|
||
Attachment #659357 -
Flags: review?(bzbarsky)
Comment 3•12 years ago
|
||
Comment on attachment 659356 [details] [diff] [review] Change some uses of nsChangeHint_ReflowFrame to check nsChangeHint_NeedReflow. (, patch 1) r=me
Attachment #659356 -
Flags: review?(bzbarsky) → review+
Comment 4•12 years ago
|
||
Comment on attachment 659357 [details] [diff] [review] Rename nsChangeHint_ReflowFrame to nsChangeHint_AllReflowHints to make it clearer that it's the one that contains multiple bits. (, patch 2) r=me
Attachment #659357 -
Flags: review?(bzbarsky) → review+
Assignee | ||
Comment 5•12 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/b4d8b251f64d https://hg.mozilla.org/integration/mozilla-inbound/rev/93f98bebfe39
Comment 6•12 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/b4d8b251f64d https://hg.mozilla.org/mozilla-central/rev/93f98bebfe39
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla18
You need to log in
before you can comment on or make changes to this bug.
Description
•