1311928 - the video player on fivethirtyeight.com would not work.

Status: RESOLVED FIXED

(Core Graveyard :: Plug-ins, defect)

Description

[Alice0775 White]

[Tracking Requested - why for this release]: Video would not playback.


+++ This bug was initially created as a clone of Bug #1306465 +++

Spin-off from Bug 1306465 Comment #24.



Sample URL: http://fivethirtyeight.com/features/late-night-podcast-a-nasty-third-debate/
scroll down to find the video.

The video itself is HTML5. However, if the user has Flash installed, then a Flash Object is placed on top the video for ad purposes. While the ad will play, the video itself will be covered in white. Only the controls work.

I would guess that the problem has something to do with transparency or possibly even how you handle the wmode.


Regression window:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=02c69f4f896255189ce2f9f4e0d875e383bcfbd7&tochange=a1bd47d76f71162534090485acc57866dcd55eef

Regressed by: bug 1229961 on trunk

Comment 1

[Terrell Kelley]

To make this clear, this is only with async plugins turned on. It works normally if dom.ipc.plugins.asyncdrawing.enabled is set to false.

Comment 2

[Terrell Kelley]

A quick fix might be to create a site blacklist for the dom.ipc.plugins.asyncdrawing.enabled option. Ideally, we'd figure out why the player was covered in white. Do note that the audio still played, BTW. 

I do note that I used to use a plugin that changed the wmode for Flash (so I'd get hardware acceleration), and it caused similar symptoms sometimes. I don't remember if the problem occurred on FiveThirtyEight, but I remember that videos around the web, including embedded YouTube videos, would have the controls not show.

Comment 3

[u554753]

Reproducible on Windows 10
CPU             Intel Core i7-4790 CPU @ 3.60GHz
RAM             16.0 GB
Graphics        NVIDIA GeForce GTX 745
Version 	49.0.2
Build ID 	20161019084923
User Agent 	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0
Shockwave Flash:23.0.0.162
Aynchronous Rendering Plugin - true
e10s - Disabled

Comment 4

[Terrell Kelley]

I tested it on the Basic renderer, the Direct3D9 renderer, and the Direct3D11 Warp renderer. My Graphics is an Intel G45, so the Direct2D renderer is blacklisted. (Before it was, I was able to use it, but it had glitches.)

Comment 5

[Jim Mathies [:jimm]]

Involves a flash applet on top of other content with incorrect clipping. Sounds similar to bug 1306698.

Comment 6

[Alice0775 White]

Attachment: reduced testcase

This should be duplication of Bug 1312242.
Adding <param name="bgcolor" value="#ffffff" /> seems to fix the problem.

Comment 7

[Terrell Kelley]

Confirm that the test case produces the same symptoms here. Using the Basic Renderer on the official Linux version. (I've disabled the pref on my Windows machine.)

Comment 8

[Ritu Kothari (:ritu) (Inactive, please n-i to RyanVM, jcristau, or pascal)]

We've reverted the pref dom.ipc.plugins.asyncdrawing.enabled to false in 50.0b10. 50 should be unaffected now. Wontfix for 50 (when the pref is set to true).

Comment 9

[Terrell Kelley]

Can the pref be sent to 49 as well? Doesn't seem like the kind of thing you want to leave.

Comment 11

[Marcia Knous [:marcia]]

Adjusting tracking flags since this is a dupe. Will move them over to the dupe bug.

Comment 12

[Andrew Overholt [:overholt]]

I'm making the release status the same as bug 1312242 (with a ? for 51 since that bug's patch may still be uplifted).