We need to implement OMTC for Direct3D 9. This bug will track that implementation.

We've got shadow layers for D3D9 working so that should make D3D9 a lot easier then D3D10.

Using this as a meta bug for anything D3D9 OMTC related.

I'm wanting to test this. How to I enable it? Every time I try, I get forced to Direct3D 11 OMTC instead, even if I have preferD3D9 set. I've already tested D3D11 OMTC and found it was pretty good (save for a certain annoying bug), and D3D9 OMTC is supposed to be even better.

(In reply to Terrell Kelley from comment #3) > I'm wanting to test this. How to I enable it? Every time I try, I get forced > to Direct3D 11 OMTC instead, even if I have preferD3D9 set. I've already > tested D3D11 OMTC and found it was pretty good (save for a certain annoying > bug), and D3D9 OMTC is supposed to be even better. You need to disable direct2d also (about:config pref) with that and preferD3D9 you should get d3d9 (check in about:support), if you don't, please file a bug. d3d9 and 11 should be about equally well supported (i.e., not quite there yet, but almost). Performance should be better with 11. You might (with d3d9) get a crash when the thumbnailer background process fails (which happens more often than I'd like). Working on fixing that...

Nope, not working, at least, on Firefox 24. Direct2D is already disabled for my graphics card version (as it produces black boxes where text is supposed to be), but I tried disabling it manually anyways. No luck. Note, Direct2D doesn't seem to activate in D3D11 OMTC for me, either. I get no black boxes, my canvas renderer still shows Skia and Cairo, and my content renderer still says none instead of Direct2D. If Direct2D is the only difference between these implementations, perhaps I am in D3D9 but about:support is displaying information improperly. (If it helps determine which is which--the "annoying bug" I mentioned earlier is content disappearing if I scroll too far down on anything but the main scrollbar. The content comes back only after clicking a bunch of times where the content is supposed to be or scrolling up a bunch of times.) Anyways, I will now download the latest Nightly and test it there, and will file a bug if I still run into the problem in my first paragraph. Since this is the meta bug, I'll link the bug here. (Should I mark it as blocking, depends on, or neither? Or is that something only devs can do?)

Actually, in Nightly (2013-10-14), I seem to have the opposite problem. I can't force on D3D11 OMTC. Forcing on Direct2D doesn't seem to work. It enables Direct2D for the content backend (which does not show any black boxes), but not for canvas, and I'm still stuck in D3D9 for layers. Forcing on Direct2D does work fine if OMTC is disabled. And I do get black boxes. (Although, if I only enable D2D for the content backend, they go away permanently after I click on anything after startup--I'm quite impressed!)

This work is now better tracked by bug 899787.