I agree the string is confusing. 
1) If it's domain-specific, we could use a string like "Show pop-ups on this site"
2) "for this site" would be clearer than "always"

"Show pop-ups on this site" won't fit in a button. Per discussion with hannahs@, we could use the mini infobar style to accommodate this CTA and since the body string is so short. Quickie examples attached.

Deleted: popup blocked-mini info bar.png 13.9 KB

	popup blocked-mini info bar.png 13.9 KB View Download

Thanks! I like them both, with a preference for the slightly longer one ("Show popups on this site"). I think that does a good job of indicating that "show" refers to the popup, and not the infobar.

Nit: do we use "popup" or "pop-up"? I actually don't remember.

I see my own string reflects our general inconsistency in the UI:

~6 instances of "pop-up"
~10 of "popup"
~2 instances of "pop up" [noun], which I wouldn't recommend

Typically, hyphen usage in compound words drops off after a word becomes commonplace. For now, based on a quick Google Trends search, I'm inclined to keep the hyphen. 
 

Cleaned up the mock w/the preferred string. The longer string is my preference, too. 

Assigning to Hannah to review & for next steps.

Deleted: Pop-up blocked-mini-infobar-2lines.png 7.3 KB

	Pop-up blocked-mini-infobar-2lines.png 7.3 KB View Download

Looks like other browsers tend to use pop-up, though MDN uses popup: https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XUL/PopupGuide

I'm fine either way.

I think we should be as consistent as possible with permission prompts. They currently don't emphasize that the decision is permanent for the site (especially on desktop), and if we do something like that here we should update those prompts too.

qq: Most infobars on Android use a linear layout with wrapped text. Which existing infobar has "title + subtitle" layout that the proposed design in #4 shows?