Closed
Bug 1219991
Opened 9 years ago
Closed 9 years ago
make RestyleManager::{Begin,End}ProcessingRestyles private
Categories
(Core :: CSS Parsing and Computation, defect)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
FIXED
mozilla45
Tracking | Status | |
---|---|---|
firefox45 | --- | fixed |
People
(Reporter: heycam, Assigned: heycam)
Details
Attachments
(1 file)
1.38 KB,
patch
|
dholbert
:
review+
|
Details | Diff | Splinter Review |
The only callers of these two methods are RestyleTracker, which is a friend of RestyleManager, so let's just make them private.
Assignee | ||
Comment 1•9 years ago
|
||
Comment 2•9 years ago
|
||
Comment on attachment 8680961 [details] [diff] [review] patch r=me
Attachment #8680961 -
Flags: review?(dholbert) → review+
Comment 3•9 years ago
|
||
(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.)
Assignee | ||
Comment 4•9 years ago
|
||
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.
Comment 6•9 years ago
|
||
Oh, right -- I missed that BeginProcessingRestyles is called in a different scope from EndProcessingRestyles there. Never mind for now, I suppose.
Comment 7•9 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/198cb59335e7
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
status-firefox45:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla45
Comment 8•9 years ago
|
||
bugherder uplift |
https://hg.mozilla.org/releases/mozilla-b2g44_v2_5/rev/198cb59335e7
status-b2g-v2.5:
--- → fixed
Comment 9•9 years ago
|
||
removing the b2g 2.5 flag since this commit has been reverted due to an incorrect merge, sorry for the confusion
status-b2g-v2.5:
fixed → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•