Flash player not working in chrome incognito.

[Guest]

Imgur: The most awesome images on the Internet

Can't use the flash player in incognito please help.

[jeromiec83223024]

MLB uses Adobe Access (DRM) and Adobe Primetime (broadcaster-grade video streaming). 

While Flash Player supports these, the code the actually processes the video streams is contributed from those teams.  MLB's streaming division (MLB.AM) has deep technical expertise, direct access to telemetry about how their video feeds perform in the field, and direct support channels with the Primetime and Access folks.  They're really in the best position to investigate and solve this.

[daring_Odyssey15A8]

I'd still like to comment on the Flash Player being disabled in Incognito mode. I'm not worrying about running Flash in Incognito personally, but our users running the site in regular mode.

I understand that the "Site Engagement Score" in Incognito mode is 0, and Flash doesn't run by default. But how come Flash still doesn't run, even after clicking Allow in the Run Flash -dialog!?

Is this behaviour expected and how can I be sure it doesn't happen in non-Incognito mode?

I've got the before-mentioned flags set to default.

[jeromiec83223024]

It's hard to say without talking about your specific case, and we're heading off-topic now.  It might be better to start a new thread with a link to a page that demonstrates the problem, since everyone on this thread gets an email when there's activity here. 

Where I usually see this break down is when content providers are doing something clever when using JavaScript to inject Flash Player into the page DOM, and the code (reasonably) assumes that Flash Player would be visible as an installed plug-in at launch.

If your logic checks to see if Flash is available before injecting the embed/object tags, but Chrome is interceding, then you might land in a code branch that handles the case where Flash isn't installed, instead of ultimately embedding the SWF at the right position and size (i.e. at the point that the user has authorized Flash, you're way past the point in JavaScript where that would have actually helped).

[Guest]

Today my chrome is updated to version 61 (stable version) and the flags (chrome://flags/#prefer-html-over-flash and chrome://flags/#run-all-flash-in-allow-mode) are not found in this version.  The problem that 'Flash Player being disabled in Incognito mode' re-appeared again in Chrome 61.  Any other workaround?

[Guest]

Same issue with Chrome using it normally or in Incognito. Do you see the Plugin Blocked slide into view in the right side of the address bar? You won't see it in Incognito.You can click that and click Run all plugins this time and it seems to help but it's not a work around nor a fix.

Google should've left the setting in chrome//:flags alone but they removed it. Basically it isn't Adobe's fault and they can't fix something that isn't there for them to fix and I'm sure Google will tell them to buzz off.

Sorry if this doesn't help but I think we need to be talking to Google and not Adobe.

[_maria_]

Please refer to Google's support page Use or fix Flash audio & video - Computer - Google Chrome Help for assistance.

If Flash installation completed without error, it's most likely installed correctly.  If you continue to experience issues after working through Google's support document, please contact Google for assistance as it's their browser blocking Flash Player.

[SiRKemp]

My Chrome updated this morning.  Flash works fine on the normal Chrome window, but not on incognito.  Followed all the steps listed below but none work, chrome://flags/#run-all-flash-in-allow-mode, etc are no longer available to be changed.  Any more ideas?

[jeromiec83223024]

No.  This is an intentional change on Google's part.  They will continue to increase friction for users that depend on Flash content in an effort to force content providers away from using Flash.

Your options are pretty much limited to complaining to Google, and/or voting with your feet.

[jackmeow]

It's really not a matter of voting with one's feet when one is required to use Flash to take classes or complete required training. WE may know better, but the developers of the training do not. How about putting pressure on the content developers. There is no great uprising of users demanding more Flash content.

[jeromiec83223024]

Yes, that is the explicit intent of Google's change.  If content providers see an uptick in support requests, they're going to be more inclined to make the investment to migrate.  In fact, because the major browser manufacturers are mostly implementing these controls in tandem, your options are pretty limited.  That said, because they're all implementing these controls in slightly different ways, being flexible about which browser you use is a good first step in finding a workaround when problems arise with your browser of choice.

If you really do rely on a specific piece of content and can't find a similar competing service that has already made the investment to migrate, then applying pressure to the content provider is a great idea.  It's going to get significantly harder to run Flash Player, and if they haven't made the jump, it will ultimately hit their bottom line.

[Lander1]

Today my chrome browser was updated to version 62.0.3202.62 and I can not view flash content, I see the following poster (above shown in the image) and I give it to allow but it does not work, does anyone know how to fix it?

I have read the comments of the post and in this new version has disappeared the option '' HTML to prefer flash '' of the section flags. In incognito window it appears that I have disabled the flash and normal window works me correctly

[_maria_]

Google removed  'Prefer HTML over Flash' (and 'Run all Flash in Allow mode') flag in Chrome 61, not 62.  See https://bugs.chromium.org/p/chromium/issues/detail?id=709550 for more information.  I recommend reading through the bug record, especially comments by laforge@google.com

Since the functionality marked 'correct' in this discussion topic no longer exists, this topic is no longer relevant to today's version of Chrome, therefore I'm locking this discussion topic.

[graviton_beam]

If none of these solutions are working for you, what solved it for me is going to the lock icon at the top left and choosing disable on javascript.