Closed
Bug 1035833
Opened 10 years ago
Closed 10 years ago
Fix layersId allocation in nested content process
Categories
(Core :: Graphics: Layers, defect)
Core
Graphics: Layers
Tracking
()
RESOLVED
FIXED
mozilla33
People
(Reporter: kanru, Assigned: kanru)
References
Details
Attachments
(1 file)
|
1.32 KB,
patch
|
mattwoodrow
:
review+
|
Details | Diff | Splinter Review |
We only want to call CompositorParent::AllocateLayerTreeId() in the chrome process.
Attachment #8452307 -
Flags: review?(bjacob)
|
||
Comment 1•10 years ago
|
||
Comment on attachment 8452307 [details] [diff] [review] patch Review of attachment 8452307 [details] [diff] [review]: ----------------------------------------------------------------- I don't know RenderframeParent enough to understand whether or not it's normal that we would hit that code in non-parent process. Matt?
Attachment #8452307 -
Flags: review?(bjacob) → review?(matt.woodrow)
|
||
Updated•10 years ago
|
Attachment #8452307 -
Flags: review?(matt.woodrow) → review+
|
Assignee | |
Comment 2•10 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/c125cf6a0a94
|
||
Comment 3•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/c125cf6a0a94
Assignee: nobody → kanru
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla33
You need to log in
before you can comment on or make changes to this bug.
Description
•