Closed Bug 1094349 Opened 7 years ago Closed 6 years ago
Various rendering problems since introduction of D2D 1
We should probably disable this on Aurora.
Seems that disabling it is causing some issues as well?
(In reply to Milan Sreckovic [:milan] from comment #2) > Seems that disabling it is causing some issues as well? Fixing that should be a high priority. We don't want to repeat what happened with OMTC.
For reference, I'm also seeing some rather strange rendering artifacts on my primary desktop since D2D 1.1 landed. I'm going to force it off and see if things are okay there.
Removing d2d 1.1 from the backends list on my desktop (with gtx 670) produces the same missing bitmaps in chrome & content that I see on my laptop. So I don't think that's a driver issue.
You need to disable both USE1_1 and remove direct2d1.1 from the backend lists. Let me know if that works better.
That fixes the missing bitmaps on both my machines, thanks.
[Tracking Requested - why for this release]: D2D 1.1 is still active on 35, and rendering issues are something we need to be careful with right now.
7 years ago
Assignee: nobody → bas
Tracking (for what Kairo said).
(In reply to Sylvestre Ledru [:sylvestre] from comment #9) > Tracking (for what Kairo said). Well, we have since disabled D2D 1.1 on Aurora, so it's unaffected now. Or rather, the bugs are disabled. ;-)
Milan, do you know what is the plan with D2D for 36? Thanks
Summary: Various rendering problems since introduction of D2D 1.1 on Aurora → Various rendering problems since introduction of D2D 1.1
(In reply to Sylvestre Ledru [:sylvestre] from comment #12) > Milan, do you know what is the plan with D2D for 36? Thanks I'll let Bas answer.
Flags: needinfo?(milan) → needinfo?(bas)
(In reply to Sylvestre Ledru [:sylvestre] from comment #12) > Milan, do you know what is the plan with D2D for 36? Thanks My hope is it can stay on. I believe there's still one or 2 issues which might still need to be fixed though. As far as I know however, most of the glitches should be gone and fixed.
Bug 1091903 is fixed now. In addition to that this bug was really more about wrongly disabling D2D 1.1 than anything else.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.