Closed
Bug 1281834
Opened 8 years ago
Closed 3 years ago
Remove layers.use-image-offscreen-surfaces preference
Categories
(Core :: Graphics, defect, P3)
Core
Graphics
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: lsalzman, Assigned: lsalzman)
References
Details
(Whiteboard: [gfx-noted])
Attachments
(1 file)
(deleted),
patch
|
Details | Diff | Splinter Review |
The layers.use-image-offscreen-surfaces preference was only really useful during a transitional period where we wanted to keep xrender for compositing but disable it for content rendering.
Since we have moved to universally disabling xrender, this preference just becomes an annoyance when a user wants to toggle xrender back on in, for example, remote usecases.
Assignee | ||
Comment 1•8 years ago
|
||
This patch makes xrender all-or-nothing based on the gfx.xrender.enabled preference. You either get all of xrender or none of it, which makes it easier to figure out which prefs you need to toggle.
Attachment #8764640 -
Flags: review?(jmuizelaar)
Assignee | ||
Comment 2•8 years ago
|
||
May shelve this until we determine if we just want to always force use-image-off-screen-surfaces instead, as that would let us not have to deal with xrender for content in any case. The issue is I guess if we can still get around our performance issues in remote X setups by allowing compositing to use xrender even if not content.
Whiteboard: [gfx-noted]
Updated•7 years ago
|
Priority: -- → P3
Comment 3•3 years ago
|
||
The string layers.use-image-offscreen-surfaces
no longer exists in-tree:
https://searchfox.org/mozilla-central/search?q=layers.use-image-offscreen-surfaces&path=
I think we can call this WORKSFORME, i.e. the pref has already been removed.
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•