[1] http://ie.microsoft.com/testdrive/info/FrequentlyAskedQuesti...
[1] http://ie.microsoft.com/testdrive/info/FrequentlyAskedQuesti...
http://hacks.mozilla.org/2010/09/hardware-acceleration/
http://blog.chromium.org/2010/09/unleashing-gpu-acceleration...
If Microsoft wanted to support GPU acceleration through an alternate rendering path like two other browsers are doing on XP, they would have done so.
I find it more likely to conclude that they just didn't want to support XP and developed a browser GPU acceleration engine that wouldn't support it as a result of this high-level decision.
You can point at the FAQ all day, but you can't deny that there is a way to do GPU acceleration of web content on XP.
1) They don't want people using XP. If other browser vendors want to take it on, I think MS has decided that they're fine with that. But they don't want to enable XP anymore.
2) The test matrix is a huge test cost. Doing XP means cutting something else. I think they decided that the cost of supporting XP wasn't worth it when they looked at how it effected their roadmap.