This is a bug for tracking all issues which prevent Direct2D from being enabled by default, on -some subset- of hardware.
Let's get this in for beta 4!
Given the number of dependent bugs for this, is this actually going to make it for beta4?
(In reply to comment #2)
> Given the number of dependent bugs for this, is this actually going to make it
> for beta4?
I don't think all the dependent bugs actually block Beta4. Some of them can be handled after beta4 I think. We're doing what we can, in any case.
D2D was re-enabled http://hg.mozilla.org/mozilla-central/rev/f2959b949445. Let's hope it sticks.
Why isn't this bug blocked by bug 532106?
Until it's fixed (by the patch for bug 130078 I suppose) D2D is making browsing painful. I need to go to another tab and then switch back before I see any content.
OS: Windows Vista
Graphic card: ATI Mobility Radeon HD 3400 Series (DirectX 10.1)
Drivers: Catalyst 10.7
(In reply to comment #5)
> Why isn't this bug blocked by bug 532106?
> Until it's fixed (by the patch for bug 130078 I suppose) D2D is making browsing
> painful. I need to go to another tab and then switch back before I see any
> OS: Windows Vista
> Graphic card: ATI Mobility Radeon HD 3400 Series (DirectX 10.1)
> Drivers: Catalyst 10.7
Because bug 130078 blocks Beta5, and we need to start getting D2D tested now or it won't be ready. We will do what we can to find a temporary fix that will cover the beta 4 testing period. It's possible to try beta 4 without D2D by setting mozilla.widget.render-mode to 0 in about:config.
Sadly, this needs to slip to beta 5.
I believe that this was turned on in http://hg.mozilla.org/mozilla-central/pushloghtml?changeset=42545f8d4b10, yes?
Sorry, ignore comment 8 - that's bug 549116 (Enable D2D by default)
We enabled it by default a couple of weeks ago; we'll leave this open as a tracking bug, but there's no need for it to block beta 5.
Closing this since Direct2D is enabled by default now.