Closed Bug 1219991 Opened 9 years ago Closed 9 years ago

make RestyleManager::{Begin,End}ProcessingRestyles private

Categories

(Core :: CSS Parsing and Computation, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla45
Tracking Status
firefox45 --- fixed

People

(Reporter: heycam, Assigned: heycam)

Details

Attachments

(1 file)

The only callers of these two methods are RestyleTracker, which is a friend of RestyleManager, so let's just make them private.
Attached patch patchSplinter Review
Assignee: nobody → cam
Status: NEW → ASSIGNED
Attachment #8680961 - Flags: review?(dholbert)
Comment on attachment 8680961 [details] [diff] [review]
patch

r=me
Attachment #8680961 - Flags: review?(dholbert) → review+
(Tangent/speculation: I wonder if we should really be using an RAII object to make these {Begin|End}ProcessingRestyles calls?

Maybe it's not worth it, since they're only called once -- from RestyleTracker::DoProcessRestyles(). Still, if we added an early-return in between the calls for some reason, we'd probably get into trouble from forgetting to call EndProcessingRestyles before the return -- and an RAII object would save us from that.)
Yes, although it looks like it would be tricky to do that with the RAII ReframingStyleContexts being used there too, as the two scopes wouldn't nest.
Oh, right -- I missed that BeginProcessingRestyles is called in a different scope from EndProcessingRestyles there. Never mind for now, I suppose.
https://hg.mozilla.org/mozilla-central/rev/198cb59335e7
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla45
removing the b2g 2.5 flag since this commit has been reverted due to an incorrect merge, sorry for the confusion
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: