Closed
Bug 1588837
Opened 5 years ago
Closed 5 years ago
Disable WebRender on some older Intel devices
Categories
(Core :: Graphics: WebRender, enhancement)
Core
Graphics: WebRender
Tracking
()
RESOLVED
FIXED
People
(Reporter: jrmuizel, Assigned: jrmuizel)
Details
Attachments
(1 file)
47 bytes,
text/x-phabricator-request
|
lizzard
:
approval-mozilla-release+
|
Details | Review |
This is a risk mitigation that would be super nice to get into 70.
Assignee | ||
Comment 1•5 years ago
|
||
Assignee | ||
Comment 2•5 years ago
|
||
Comment on attachment 9101311 [details]
Bug 1588837. Disable WebRender on some older Intel devices.
Beta/Release Uplift Approval Request
- User impact if declined: We'll run WebRender on some machines where it doesn't run that great.
- Is this code covered by automated tests?: No
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): This just removes some device ids. It should be basically 0 risk.
- String changes made/needed:
Attachment #9101311 -
Flags: approval-mozilla-release?
Assignee | ||
Comment 3•5 years ago
|
||
[Tracking Requested - why for this release]: Reduce WebRender Intel risk
tracking-firefox70:
--- → ?
Assignee | ||
Comment 4•5 years ago
|
||
One of the big motivations for this is bug 1576637.
Updated•5 years ago
|
Comment 5•5 years ago
|
||
Discussed with jeff, we don't want to land this on m-c because we want to keep seeing issues from affected users in nightly.
Comment 6•5 years ago
|
||
Comment on attachment 9101311 [details]
Bug 1588837. Disable WebRender on some older Intel devices.
OK for uplift to m-r, we'd like to block WR for particular drivers.
Attachment #9101311 -
Flags: approval-mozilla-release? → approval-mozilla-release+
Updated•5 years ago
|
Assignee: nobody → jmuizelaar
Comment 7•5 years ago
|
||
bugherder uplift |
Comment 8•5 years ago
|
||
Based on comment 7, I am marking this issue as fixed.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•