Closed
Bug 858144
Opened 11 years ago
Closed 11 years ago
Figure out how to deal with blacklisted hardware in metro firefox
Categories
(Core :: Graphics, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 870390
People
(Reporter: jimm, Unassigned)
References
Details
In metrofx, we force d2d fully on and ignore blacklisted devices. When users use metrofx on these devices though all sorts of things can go wrong with rendering. We should to investigate a couple avenues: 1) simplifying our use of d2d (maybe forcing cairo to gdi, turning off layers, or?) on blacklisted hardware and only relying on d2d to paint to the screen. 2) dumping these users out to desktop 3) ?? It will also be interesting to see how omtc plays into this.
Reporter | ||
Updated•11 years ago
|
Reporter | ||
Comment 1•11 years ago
|
||
oops.
Comment 2•11 years ago
|
||
(In reply to Jim Mathies [:jimm] from comment #0) > In metrofx, we force d2d fully on and ignore blacklisted devices. When users > use metrofx on these devices though all sorts of things can go wrong with > rendering. We should to investigate a couple avenues: > > 1) simplifying our use of d2d (maybe forcing cairo to gdi, turning off > layers, or?) on blacklisted hardware and only relying on d2d to paint to the > screen. > 2) dumping these users out to desktop > 3) ?? > > It will also be interesting to see how omtc plays into this. This has all been thought about, OMTC will support D3D11 (Level 9.3) composition with software page drawing. It fully supports our blacklist as far as Direct2D is concerned.
Reporter | ||
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•10 years ago
|
OS: Windows 8 Metro → Windows 8.1
You need to log in
before you can comment on or make changes to this bug.
Description
•