Able to reproduce the issue on Windows 10 with latest Chrome beta i.e, 60.0.3112.40 and specific to Windows(Unable to reproduce the issue in Mac 10.12.5), This is a regression since the same works fine on M59(59.0.3071.115)stable.



Note : On Chrome M61 we have another issue where selecting the prompt to allow flash to run doesn't get honored.

So, just testing the site.  It doesn't appear to be HTML5 by Default related.  The black content appears after Flash has been granted access to a site.  Once enabled I can hear the audio (i.e. it sounds like the swf is playing).

It's generally unclear if this is a web platform issue or a Flash issue.  A bisect will be important for clarifying this case.

Able to reproduce the issue on windows 7 using chrome version 60.0.3112.40 and it is working fine on Stable 59.0.3071.115 and canary 61.0.3142.0.
Please find the reverse bisect information as below

Narrow Bisect::
Good :: 60.0.3112.45   --    (build revision  474897)
Bad :: 60.0.3112.42   --    (build revision  474897)

Unable to provide the tool bisect as the good and bad builds are from branch builds.Hence providing manual CL

Omahaproxy Change Log::
https://chromium.googlesource.com/chromium/src/+log/60.0.3112.42..60.0.3112.45?pretty=fuller&n=10000

Unable to find the suspect from the above CL.
Could any one from Dev team please help us in assigning to the appropriate owner for this issue.

Thanks,

Could any dev from Internals>Plugins>Flash team please have a look into the issue as it has been marked as stable blocker.

Thanks...!!

I'm not sure that I see the case for RBS.  Things appear to be working after .40 (i.e. 60.0.3112.45) and on 61.x.

Unless I'm missing something, there doesn't appear to be an action required.  Would it be possible to reconfirm the bisect?

kavvaru@, can you please confirm the bisect?

If that CL range is correct, I'd speculate that Charlies change may have fixed the underlying issue.

https://chromium.googlesource.com/chromium/src/+/c958784507ff188871ddbe78461876aa8463d3cd

FWIW, I think my CL should only affect things if an interstitial page is showing, but it's possible.  Agreed that it makes sense to close if no one can repro on 60.0.3112.45 or newer.

Yes, got the same bisect again.
Able to reproduce the issue on build 60.0.3112.42.

Seems this is fixed in latest beta 60.0.3112.50 as unable to reproduce the issue.

greg.lee@@ Could you please check the issue on latest beta 60.0.3112.50 and confirm from your end.

Thanks,

Fix confirmed on beta 60.0.3112.50. Can no longer repro.

[Auto-generated comment by a script] We noticed that this issue is targeted for M-60; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-60 label, otherwise remove Merge-TBD label. Thanks.