10

Something that Firefox and Chrome have in common is the ability to limit which extensions run in Private Browsing mode. The default is to not permit an extension in Private Browsing mode, unless manually and expressly permitted to run in private browsing.

This doesn't seem to be the "done" thing in Safari though, but there may be a case to be made for considering it.

If people use Orion for its plethora of extensions via Chrome and Firefox stores, they will no doubt at some point start adding untrustworthy ones that collect data. While those stores might try to stop this, if someone is in private browsing, they likely are trying to signal they'd like to try limit what is being exposed. Limiting which extensions run in this context perhaps makes sense? On the other hand, maybe it will confuse them if extensions aren't available in private browsing mode until they enable them?

  • Vlad replied to this.

    gp Any idea what would be the simplest way to do this UX wise?

    • gp replied to this.

      Vlad From a UX perspective, probably a toggle a bit like you have for enabling/disabling the extension, but labelled for enable/disable in private browsing mode?

      As an example, Firefox tucks it away in a sub-menu after you manage the extension:

        We can have an option "Allow in Private Windows" in extension icon context menu and Extensions menu for that extension, which would be toggleable with a checkmark (default off)

        • gp likes this.
        2 months later


        A menu for configuring the settings of browser extensions and controlling their status in private mode.

          Configuring extension settings is in preferences.

            Merged 3 posts from Extension permissions menu.
              No one is typing