Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 8 users
Status: Verified
Owner:
Closed: Jul 25
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux, Windows, Chrome, Mac
Pri: 1
Type: Bug

Blocked on:
issue 693739

Blocking:
issue 696790



Sign in to add a comment
Remove "Prefer HTML over Flash" from chrome://flags
Project Member Reported by lafo...@chromium.org, Apr 7 Back to list
Given the complete launch of HTML(5) by Default and the upcoming settings unification, we should also remove the flag to disable "Prefer...," since the behavior is no longer considered an experiment.
 
Blockedon: 693739
Do we still need this flag until we can re-enable this feature on all ChromeOS devices? (To allow admins to test on ChromeOS in advance of our re-enabling by default).
Yes, that's probably fair (and very good observation).  We need to sync back around w/ their Enterprise folks to see if they've added the necessary configuration in CPanel.  60 maybe too aggressive for this change.
Not so fast, please: for whatever reason MLB video won't even play if you have "default" on the setting. They insist you change it to "disabled" to even be able to see their video. It sucks, but I'm paying good money for that, so please don't change it.
Toggling that flag is dangerous since it allows Flash Player to run on all sites on the web (i.e. not just MLB), rather than just restricting it to origins that need it.  That recommendation unfortunately opens users to security issues and highlights why that flag needs to be removed.

(If that's their recommendation) MLB will either need to update their instructions to use site exceptions (https://support.google.com/chrome/answer/114662), which are quickly accessible from the lock icon next to the site address, or present a link to (download|enable) Flash player, which when clicked will enable Flash for that particular site... both of which are simpler than going into about://flags.
Project Member Comment 5 by bugdroid1@chromium.org, Jul 21
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/edb4808c66183027797e48416f60c3802fb62796

commit edb4808c66183027797e48416f60c3802fb62796
Author: Tommy C. Li <tommycli@chromium.org>
Date: Fri Jul 21 00:32:34 2017

[HBD] Remove HBD and Run-all-Flash from chrome://flags

These flags existed in chrome://flags as an escape hatch for users
during testing.

Now that HTML5 by Default has completely launched, they are no longer
needed.

Bug:  709550 
Change-Id: I1a140a86581483913681055c246a0c2509d783c2
Reviewed-on: https://chromium-review.googlesource.com/580331
Commit-Queue: Tommy Li <tommycli@chromium.org>
Reviewed-by: Anthony LaForge <laforge@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488516}
[modify] https://crrev.com/edb4808c66183027797e48416f60c3802fb62796/chrome/browser/about_flags.cc
[modify] https://crrev.com/edb4808c66183027797e48416f60c3802fb62796/chrome/browser/flag_descriptions.cc
[modify] https://crrev.com/edb4808c66183027797e48416f60c3802fb62796/chrome/browser/flag_descriptions.h

Project Member Comment 6 by bugdroid1@chromium.org, Jul 21
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/71bce333b862b8def630b2c581a54e28a5042308

commit 71bce333b862b8def630b2c581a54e28a5042308
Author: Tommy C. Li <tommycli@chromium.org>
Date: Fri Jul 21 16:57:10 2017

[HBD] Remove the "Run all Flash in Allow mode" feature.

We've already removed access to this feature from chrome://flags.

This just removes the now-dead implementing code.

Bug:  709550 
Change-Id: I21cd2516874722525c2ddab4a2ab0840e46d38c4
Reviewed-on: https://chromium-review.googlesource.com/580363
Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Commit-Queue: Tommy Li <tommycli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488683}
[modify] https://crrev.com/71bce333b862b8def630b2c581a54e28a5042308/chrome/browser/plugins/plugin_info_message_filter.cc
[modify] https://crrev.com/71bce333b862b8def630b2c581a54e28a5042308/chrome/common/chrome_features.cc
[modify] https://crrev.com/71bce333b862b8def630b2c581a54e28a5042308/chrome/common/chrome_features.h

Should we flip this to Fixed?
Status: Fixed
Yes! Thank you for the reminder.
Labels: TE-Verified-61.0.3163.13 TE-Verified-M61
Adding the verified label as well as 'Prefer HTML over Flash' is not present on chrome version: 61.0.3163.13 on Windows-10, Mac OS 10.12.5 and Linux Ubuntu 14.04.
709550.png
122 KB View Download
Cc: vsu...@chromium.org hsiangc@chromium.org
laforge@: does this need to fix in M-60?
Labels: -M-60 M-61
Nope, no need to merge it back.
@hsiangc - Thanks for checking!
Status: Verified
Verified with 9765.28.0/61.0/3163.41
So - I see this issue is closed... but I am confused. The main issue talked about removing the Prefer HTML over Flash flag which I get is redundant with the new settings... the the #run-all-flash-in-allow-mode flag is also being removed but is no longer supported it would seem.

We have a legacy application that we are planning to completely replace over the next two years that still uses "hidden" flash objects as part of it's infrastructure and there is no longer any way to enable those with that flag removed.

Is this intentional or an oversight? For our customers on desktops we can just send them to FF for now - but without an ability to enable this flag our ChromeOS customers are going to be SOL.
bken...@k12.com, contact me (contact form at duckware.com) -- I have some ideas for you...
bken / k12.com: The problem is with the K12 OLS system.  I signed in, took a look at the web pages, and was able to fix the pages after the fact and run Flash.

Just have your developers fix K12.com -- crazy easy.

If your "customers are going to be SOL" -- it is solely due in inaction on the part of K12.
The "prefer-html-over-flash" flag is a solution to making flash work in incognito mode. This was cited by Adobe staff about 6 months ago.
 (https://forums.adobe.com/thread/2298071)

Now that it's gone there's no way to use Flash in incognito mode. Is this intended?
@jerusanders - My recommendation would be to use the site settings menu, which you will find by clicking the icon (usually a lock or an i) in the url bar, next to the reload button.  In there you can enable Flash Player to run for a particular site.

Because incognito mode effectively is only a temporary profile, those preference selections will only exists so long as the incognito window(s) is open.
@laforge

The site settings menu is bugged in the incognito mode. The only way to get flash to work on incognito is through the removed flag 

@laforge

Yeah, it doesn't work, it seems to ignore the site settings menu. Even "Click to run Flash" thing just causes the page to refresh with the flash still blocked.
Confirmed, with the flag removed I cannot enable flash video in incognito mode.
I'm not able to replicate that behavior in incognito (i.e. all forms enablement prompts work properly).

If there is a specific site that does not work properly in incognito, please file a separate bug.
Comment 23 by estephan...@gmail.com, Sep 19 (5 days ago)
I have the issue in icongnito mode as well, earlier it was only this setting "Prefer HTML over Flash" tha fixed it and it's definitely removed now in 61.0.3163.91! Let's hope that we find another workaround soon!
Comment 24 by sheacma...@gmail.com, Today (4 hours ago)
Trouble is site exceptions are not working. As a result auto playing will not work. i have to actually click on a play button to make content run. The flag that was removed in question is causing me alot of trouble now since it was removed. I personally would like to see it reinstated or turned into a setting that allows autoplay.
Sign in to add a comment