This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Natao arisiva ity resaka mitohy ity. Mametraha fanontaniana azafady raha mila fanampiana.

Pop-up windows exceptions not working in private mode (Firefox 87.0)

  • 1 valiny
  • 3 manana an'ity olana ity
  • 1 view
  • Valiny farany nomen'i VVG

more options

Hi,

After an update on Firefox 87.0 the pop-up exceptions defined are not working in private mode. A yellow bar appears that tells me that prevent the popups. If I choose to allow the popups with the button on the left of url then the url is added on exceptions/allowed window with a ^privateBrowsingId=1 marked in the url. However this is not persisted on a next run of firefox on private mode.

If someone have setup exceptions is there for a reason and should not be broken in private mode. I also cannot add ^privateBrowsingId=1 on my own in the url on the exceptions, as it appeared as %5 in exceptions and it does not work to allow pop-up.

Thanks

Hi, After an update on Firefox 87.0 the pop-up exceptions defined are not working in private mode. A yellow bar appears that tells me that prevent the popups. If I choose to allow the popups with the button on the left of url then the url is added on exceptions/allowed window with a ^privateBrowsingId=1 marked in the url. However this is not persisted on a next run of firefox on private mode. If someone have setup exceptions is there for a reason and should not be broken in private mode. I also cannot add ^privateBrowsingId=1 on my own in the url on the exceptions, as it appeared as %5 in exceptions and it does not work to allow pop-up. Thanks

All Replies (1)

more options

This bug is still unfixed on 88.