Show option to allow current popup in popups info bar for "about:blank"

NEW
Unassigned

Status

()

Firefox
General
4 years ago
4 years ago

People

(Reporter: tanvi, Unassigned)

Tracking

34 Branch
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
Created attachment 8481550 [details]
Popups infobar

When I visit https://people.mozilla.org/~tvyas/windowopen5.html, it attempts a window.open to about:blank.  This is blocked by Firefox with an infobar.  The options in the infobar are:
* Allow popups for people.mozilla.org
* Edit popup blocker preferences
* Don't show this message when popups are blocked.

There is no option to allow the popup for now.  Often a user isn't sure if they want to whitelist popups for the site forever, they may just want to see what the first popup is before deciding if it's helpful to allow or annoying to allow.

Can we add an option for this?  If I recall correctly, we used to have one.  Thanks!

Comment 1

4 years ago
This is only broken for about:blank, as far as I can tell. If I modify your testcase to use "www.mozilla.org", I see the option fine (admittedly I'm testing on beta - it's possible this regressed on Nightly for all sites, but about:blank hasn't worked since at least early 2013 (noticed when I started regression hunting convinced that this was a regression :-) ) ).

Can you confirm if you're just seeing this with about:blank?
Flags: needinfo?(tanvi)
Summary: Add option to allow current popup in popups info bar → Show option to allow current popup in popups info bar for "about:blank"
(Reporter)

Comment 2

4 years ago
Yes you are right:
https://people.mozilla.org/~tvyas/windowopen4.html

I see the option for mozilla.org.

(Just fyi, I also have some other test cases that I wrote for a different purpose:
https://people.mozilla.org/~tvyas/windowopen.html
https://people.mozilla.org/~tvyas/windowopen2.html
https://people.mozilla.org/~tvyas/windowopen3.html
)
Flags: needinfo?(tanvi)
You need to log in before you can comment on or make changes to this bug.