Bug 120447 – [Windows] Video inside a web page always falls back to non-hardware accelerated

• Status: RESOLVED
• Resolution: DUPLICATE
• Component: Media

[Brent Fulgham]

If you render a web page that embeds a video element, WebKit is turning off compositing mode forcing the system to render through the non-hardware accelerated path.

This is happening because RenderLayerCompositor::computeCompositingRequirements initially decides to turn compositing off (since the media element is usually represented as a static image before playing).

Once the user interacts with the media element (to scrub video or play the movie), RenderLayerCompositor::computeCompositingRequirements recognizes that it needs to begin compositing and switches to the correct mode.  However, the media player element has already been constructed in "non-hardware accelerated mode", and continues its lifetime without using hardware acceleration.

We need to do one of the following:
1. When the render tree switches to compositing mode, destroy/recreate the player
-or-
2. Somehow attache the D3D device to the player after construction?

[Brent Fulgham]

*** This bug has been marked as a duplicate of bug 120448 ***