Demo of it behaving correctly after a few kills.

Deleted: flash_not_running_after_repeat_kill.mov 1.1 MB

flash_not_running_after_repeat_kill.mov 1.1 MB Download

I've seen unpredictable behavior here as well. Sometimes i see pages not asking and just failing (telling me to install flash), other times i see flash running when set to ask, without asking.

I also see this on M55. 

I doubt I have anything to add to this. This seems like an issue for whoever implements the Flash plugin, or the Content Settings feature.

Oh, never mind, I see it's releaseblock.

For sites where the site engagement is sufficiently high (i.e. > 30) we will not prompt (i.e. we will allow Flash to run and not change the site's behavior).

You can check the calculated site engagement score for the sites you visit at chrome://site-engagement.

Interesting. In that case, there may just be UI issues:

- There's no indication that Flash will run — the site info bubble still says "ask".
- Certain actions trigger a permissions prompt.

This bug has been reported as M55 Beta blocker for this week Beta release on Wednesday (11/16). Please have the fix ready and merged to M55 branch latest before 4:00 PM PT tomorrow, Tuesday (11/15/). Thank you.

Since it sounds like this may be less severe than I thought, I'm going to remove the beta blocker status. Feel free to re-add it.

When url policies (see attached image) exempt a site, in the Site Permissions bubble we change the text to say "Allow (by policy)." 

Perhaps we could make this clearer, for cases where site engagement kicks in, by having similar text in that bubble saying ~ "Allow (by engagement)"... would need UX input.

Timing wise, it would probably make sense to target such a change for M56+ timeframe, since the site engagement ramping won't happen in earnest for most sites until Feb, 2017.

When simplifying the strings during the recent Material Page Info overhaul, we considered "Automatic", but ended up with "Detect".

Gentle ping, M55 is set to target stable soon. 

@ lgarron: Kindly have a look into it and please provide an update on it. Following up as issue is reported as P1.

Thanks.!

I just realized something.

Is everyone who is seeing this a Googler? There is a forced whitelist of sites applied to all logged-in Googler accounts that includes sites such as pandora.com, bbc.com, hulu.com, and twitch.tv .
sdy@, pinkerton@, any chance this might only be happening on sites listed at chrome://settings/contentExceptions#plugins ?

I can't find the existing Chromium bug about this, but see b/28124167 for the Google-internal bug.

lgarron@: I definitely noticed this first on a site that's not on the list (see the screen recording), and I'm 99% sure it was on a personal computer+profile.

@sdy : it would be great to know :
1) if site was already on chrome://settings/content, under Flash, and allowed
2) what site's chrome://site-engagement score is.

Thanks.

ericde@: Sure, happy to help.
1) It wasn't whitelisted; I checked at the time.
2) I had just ordered a pizza (5-10 minutes of interaction). I haven't been back there since I filed the bug, but I can check its current score later if that would be helpful.

[mac triage] taking this out of the triage queue, assigning based on the possibility this is UI/wording issue, but I've only spent one triagths of a time unit reading. Please reassign or triage further as appropriate.

I'm not the right person for this bug, although it's still unclear whether this is a wording issue or a bug.

Passing the hot potato to laforge@.

Flagging for privacy because this is about a content setting.

Hey Raymes,

Do you recall where the discussion about "by policy" or "by site engagement" landed?  Is this a WontFix?

I don't feel too strongly. If we do anything, I don't think it's worth doing something complicated because as the SE threshold goes up, people will see Flash automatically running less and less. So I think the most we would want is to have a string like "Run automatically". 

I'll leave this to ericde@ to decide, but I would be fine with WontFix.

getting back to this after a while...I think this is a wontfix for now. the SEI threshold is set pretty high for googlers, and will be ramping up over time as raymes@ mentions in #24 above. 

@sdy : if you disagree, please reopen and we can have a separate discussion.