Enable gfx.webrender.compositor by default on macOS
Categories
(Core :: Graphics: WebRender, enhancement, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox79 | --- | fixed |
People
(Reporter: mstange, Assigned: mstange)
References
(Blocks 2 open bugs)
Details
(Whiteboard: wr-planning)
Attachments
(2 files)
Bug 1591523 will land a first implementation of the WebRender OS compositor but it'll still be off by default.
This bug tracks the issues that need to be fixed in order to turn it on by default.
Assignee | ||
Updated•5 years ago
|
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
To clarify: WebRender will still be off by default on macOS once this lands. The goal in this bug is just to enable more efficient WebRender for people who have turned on WebRender manually.
Assignee | ||
Comment 2•5 years ago
|
||
Depends on D57070
Updated•5 years ago
|
Comment 4•5 years ago
|
||
bugherder |
Comment 5•5 years ago
|
||
Adding to Nightly 74 release notes as "The OS compositor has been enabled for macOS when WebRender is enabled"
Comment 6•5 years ago
|
||
Release Note Request (optional, but appreciated)
[Why is this notable]:
[Affects Firefox for Android]:
[Suggested wording]:
[Links (documentation, blog post, etc)]:
Comment 7•5 years ago
|
||
Comment 8•5 years ago
|
||
Bug 1592739 is being backed out for causing regressions, so this needs to be disabled as well.
https://hg.mozilla.org/integration/autoland/rev/2136aaa9de33
Comment 9•5 years ago
|
||
And on beta: https://hg.mozilla.org/releases/mozilla-beta/rev/30f86efe77d8b6807d331a62cf8189b5a2dc7503
Comment 10•5 years ago
|
||
Backout merged to central: https://hg.mozilla.org/mozilla-central/rev/2136aaa9de33
Comment 11•5 years ago
|
||
Note removed from beta release notes
Comment 12•5 years ago
|
||
Please re-nominate when the status of this bug changes.
Updated•4 years ago
|
Updated•4 years ago
|
Assignee | ||
Comment 13•4 years ago
|
||
This causes test_menulist_position.xhtml to fail pretty consistently with "Labels vertically aligned for index 6" in M-1proc(c1). Not sure why, I'll look into it. It could be a fluke.
Assignee | ||
Comment 14•4 years ago
|
||
Nevermind, that failure is from bug 1624599.
Comment 15•4 years ago
|
||
Comment 16•4 years ago
|
||
bugherder |
Description
•