User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0 Build ID: 20170302120751 Steps to reproduce: Example: http://winfuture.de/news,96550.html just want to fast-forward the Video a little bit leads to a black screen in Firefox 64bit, while sound is still playing.... In FF-32 it works fine.... With F5 you can reload the page. Until you do not fast forward the Video, everything is fine. Youtube also works, but I find this bug on many other sites. Actual results: Screen turns black and sound stays playing.... Expected results: normal video replay, like in FF-32

Maybe this is an Adobe Flash 64-bug, cause it concerns videos from Adobe flash...

Some users feedback that when visiting the live sites, if you move the mouse over the flash element, the video will turn black. It resumes display when minimize the Firefox window or switch the tab.I think it might be the same type of problem. But I can't reproduce it. The URL of this problem: https://www.douyu.com/74706 http://www.panda.tv/442657 The user's display see attachments. User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0 Build ID: 20170302120751 operating system: windows 10 pro 64-bit(10.0, build 10586)

Many people have recently encountered this problem. Around updated Firefox 52 or Flash 25? I'm not sure which is more related. I found some discuss in adobe community: https://forums.adobe.com/community/flashplayer/using_flashplayer/content?filterID=contentstatus%5Bpublished%5D~objecttype~objecttype%5Bthread%5D&query=firefox and there is also a flash bug: https://tracker.adobe.com/#/view/FP-4198373

I'm betting this is probably fixed in the latest flash release. Can someone confirm? I'm not able to reproduce on the test sites here.

(In reply to Jim Mathies [:jimm] from comment #6) > I'm betting this is probably fixed in the latest flash release. Can someone > confirm? I'm not able to reproduce on the test sites here. I can't reproduce the problem either. According to the vast majority of the feedback, the problem disappeared after the user upgraded to firefox 53. I think we can mark it has been resolved.