Do we expect most users to notice this behavior change when they see the bubble hanging off the "Flash blocked" indicator? If so, what do you think about adding some language to that bubble and/or the setting WebUI?

Deleted: flash_blocked.png 8.4 KB

	flash_blocked.png 8.4 KB View Download

That's a possibility.  Just to confirm though, that puzzle piece typically only displays when a site attempts to instantiate a small or invisible piece of Flash content and would require user interaction to uncover the message (i.e., the dialog starts in a hidden state).  For click to activate content, I don't think the Omnibox puzzle piece appears.

If we were to go that route it seems like we would need to change the behavior of the puzzle piece to be present whenever Flash was present and potentially consolidating it with the current activation UI (see attached)?

Is that what you had in mind?

Deleted: Enable Flash.png 30.6 KB

	Enable Flash.png 30.6 KB View Download

I am still trying to wrap my head around it, but my current understanding is that we are showing the broken puzzle icon in both of these cases:

 a) When Flash is BLOCK'ed by content settings, and therefore the plugin is not loaded at all. 
 b) When Flash is ALLOW'ed in "detect important content" mode, and there is Flash content on the page deemed non-important, which is loaded but paused state, requiring a click to play.

How would be able to provide more context on historical decisions?

Tommy and Rachel likely would be the ones most familiar w/ the current behavior.

In addition to a and b, there should also be a case c, for "large" or important content, which are direct embeds that present click to activate plugin placeholders but no puzzle piece in the Omnibox (see the original image that I attached, https://get.adobe.com/flashplayer/about/ illustrates this behavior well).  

There is also a case d, where sites can create links to https://get.adobe.com/flashplayer/ (i.e., download Flash links) for the user to click on to trigger the same Flash activation UI.  This case maybe less relevant in this context (i.e., Flash isn't typically instantiated site are typically just testing navigator.mimeTypes or navigator.plugins for the presence of the plugin).

In terms of usage/ importance, the uma metric Plugin.Flash.TinyContentSize provides a pretty good picture when separated by Bucket Counts (1).  Large Flash represents the bulk of current volume.

(1) - https://uma.googleplex.com/p/chrome/timeline_v2?sid=69c53416cd8198adf6a93816a1cf0ac5

qq: Why not just display an infobar (as we've done for other deprecations before, IIRC)? And pop that up whenever there is Flash content being run? This sidesteps the entire question of "when do we display the puzzlepiece" and translates it to "when does the user want to run Flash", which I'd consider the more relevant question.

E.g. I don't think we want a deprecation warning for BLOCKed content, do we?

@Rachel, yes an infobar is what I had in mind for this case.

(Apologies for my confusing comments, 918427 is close enough to this one that I got the two mixed up).

Also agreed w/ Rachel that the logic in the description can be simplified to:

If the user has changed the default to enable Flash Player manually (i.e., not via enterprise policy setting), show the standard deprecation Infobar w/ translatable warning text.

Hey folks,

I put together a quick proposal(1) with mock of what the experience could look like.

https://docs.google.com/document/d/1o32dOANC0PKqy2mMpPSwF-wmGCtqudSyQND9kg6BK-E/edit#

Deleted: Flash Deprecated.png 1.1 MB

	Flash Deprecated.png 1.1 MB View Download

I think the mock from laforge in c#13 looks good - with the possible modification of using the Flash logo in the infobar icon.

I think the logic from groby in c#6 sounds good - Since it's going to be completely gone in 2020, I think we can be 'loud' in informing users that the existing content will soon no longer work.

Updated the mock replacing the Chrome logo w/ the puzzle piece (extensions) icon that we typically associate w/ plugin UI.

Deleted: Flash Deprecated.png 1.1 MB

	Flash Deprecated.png 1.1 MB View Download

I worry that prompting for each site that uses Flash might get a little spammy for users if we do it too early (in the deprecation life cycle).  The upshot is that it very clearly tells the user what sites are making use of Flash.

Perhaps we could start w/ per session prompt when we turn Flash off by default and the user re-enables it (i.e., create a warning that's associated w/ the user's immediate action) and then graduate to prompting for each site that has Flash activated in the middle of 2020 as we approach the final deadline.

WDYT?

This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.