It seems we use simplified "Block" language now, but "Block" only applies to non-user-gesture popups.

Kendra, do you have data on how what settings people are using for popups?
And who would make a decision about adding a "Full Block" level?

Incidentally, since you used the word "adding" -- I suspect if we try to turn popup blocking into a three-state setup we're going to stall, and personally I think we would do well to stick with two states, where one of the two is "never show popups, not even on gesture" and the other is whatever.  Not sure what "adding" was intended to convey, so just throwing that out there :)

Also, if the Flash-triggered stuff should be forked off to its own bug, please feel free to do so -- I don't know exactly what the state of the world there is, only that Jochen says there are improvements that could be made but haven't been due to test coverage.

Ah, okay. So like this:
- Allow
- Default (current "Block" behaviour == allow 1 per user gesture, else block and show page action)
- Block (block alllllllllll)

That was how I had *assumed* this worked until you pointed out otherwise last night.

That sounds fine to me. Sydney folks/Emily: How much research/approval do we need for a change like that?

Uh... are we talking past each other?  I was saying that we should try and stick with two states, whatever we do (in your labels, "block" + either "default" or "allow").  And "block" should be default.

Right, I'd suggest to go for "block all popups whatsoever (default)" and "allow popups with user gesture"

as opposed to currently "allow all popups" and "allow popups with user gesture (default)"

Apparently we were.

I presume some use cases require popups without user gestures. I've certainly seen Chrome experiments that require it.

that's like the only case I know of.

That's why I said in my first comment "perhaps in either of these cases adding a whitelisted site should let it show popups without a click".

In other words, under the hood there are actually the three states you describe, and if you make an "allow" exception, it means "fully allow", even if that isn't one of the choices we give you for the global setting.

I'm a bit confused -- @jochen would you be able to clear up what the current behaviour is? I know there is a way for users to block and allow popups, and there is also a default state, but somehow this maps to only two Content Settings?

Also to answer #1, we only added popup metrics in M57 so it will be a while before we have numbers.

Removing myself as owner since this is a duplicate.