1908326 - Pop-up exceptions do not carry over to the private session

Status: RESOLVED WONTFIX

(Firefox :: Site Permissions, defect)

Description

[Przemysław Siekiera]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:128.0) Gecko/20100101 Firefox/128.0

Steps to reproduce:

1. Visit https://genshin.hoyoverse.com/en/
2. Click on the “Official Site” button in the top-right corner
3. A message saying, “Firefox prevented this site from opening a pop-up window” should show up; click on the “Options” button next to it and then the “Allow pop-ups for genshin.hoyoverse.com” option
4. Open a private window and go to https://genshin.hoyoverse.com/en/ (the same site we visited in the step 1)
5. Click on the “Official Site” button

Actual results:

The same message still pops up – “Firefox prevented this site from opening a pop-up window” – even though if we click on the “Options” button next to it, select “Manage pop-up settings…” option and click on the “Exceptions…” button to the right of “Block pop-up windows”, that site is now on the list of allowed websites.

Expected results:

I should not get that message anymore if the site is on the allowed websites list for pop-ups, and the pop-up that the site tries to open, should open, and not be blocked.

--

Also, not sure if this would be considered off-topic, but when you e.g. visit ubisoft.com in the Private Window, discard the cookie notice and click on the profile button in the top-right corner, the same message pops up, but when choose to allow pop-ups for this site, this site DOESN'T get added to the list of allowed sites (if you do this action in the private session). I guess that is intended behavior, but should it really be like that? Maybe if you're in the private session there should be two buttons for this action – one would allow pop-ups only for this session, and the second one – add it globally (and this would also add this website to the list of allowed websites for pop-ups).

--

Also, Firefox's pop-up blocker seems much stricter than Chrome's – I couldn't reproduce this on Chrome, to check how they handle it.

Comment 1

[BugBot [:suhaib / :marco]]

The Bugbug bot thinks this bug should belong to the 'Firefox::Session Restore' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Sarah Clements [:sclements]]

Moving this as it seems more related to site permissions.

Comment 3

[Emma Zühlcke [:emz]]

This is intended behavior. Site permissions added/updated in Private Browsing are separate from normal browsing and get cleared when the private browsing session ends.
While it's not recommended, you can disable that behavior via about config. Set permissions.isolateBy.privateBrowsing to false to disable the permission separation.