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

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Why does browser (FF42) act like it is in private browsing mode in a normal window on a mac?

more options

Based on the article at https://support.mozilla.org/en-US/kb/control-center-site-privacy-and-security-firefox the shield should only show in the control center when in private browsing mode. However, on a Mac, that shield appears (and is functional) when not in private browsing mode and has to be used on certain sites which have embedded twitter timelines in order to see that content. On a Windows machine, the shield only appears when in private browsing mode and when not in private mode, there's no shield and the embedded twitter timelines show up as they should. Is this a bug on the Mac version of FF42?

UPDATE: problem solved

Based on the article at https://support.mozilla.org/en-US/kb/control-center-site-privacy-and-security-firefox the shield should only show in the control center when in private browsing mode. However, on a Mac, that shield appears (and is functional) when not in private browsing mode and has to be used on certain sites which have embedded twitter timelines in order to see that content. On a Windows machine, the shield only appears when in private browsing mode and when not in private mode, there's no shield and the embedded twitter timelines show up as they should. Is this a bug on the Mac version of FF42? UPDATE: problem solved

Okulungisiwe ngu jenett

Isisombululo esikhethiwe

Thanks jscher2000.

My problem was that the tracking protection (and 'shield)' was showing up in a window that was not a private window - as a result, your step#1 did nothing to correct my problem (I had already tried that before).

The solution to my problem was simply checking and correcting the following:

" Default settings:

   privacy.trackingprotection.enabled = false
   privacy.trackingprotection.pbmode.enabled = true  "

...as per the post I linked to above ( https://support.mozilla.org/en-US/questions/1092893#answer-803473 ).

Thanks for the info which may help others hoping to solve a similar issue.

Funda le mpendulo ngokuhambisana nalesi sihloko 👍 0

All Replies (4)

more options
more options

Hi jenett, did you change a preference or did you turn off automatic private browsing mode in Privacy Preferences?

For reference by those finding this thread, those settings can be found here:

Privacy Preferences (Options), either:

Mac: "3-bar" menu button (or Firefox menu) > Preferences Windows: "3-bar" menu button (or Tools menu) > Options Linux: "3-bar" menu button (or Edit menu) > Preferences

Click "Privacy" in the left column, then you can:

(1) Uncheck the box for "Use Tracking Protection in Private Windows" if you do not want this feature

(2) If the selector in the page says "Firefox will: Never remember history" change that to "Firefox will: Use custom settings for history". Then you can view and uncheck the box for "Always use private browsing mode" if that is checked

more options

Isisombululo Esikhethiwe

Thanks jscher2000.

My problem was that the tracking protection (and 'shield)' was showing up in a window that was not a private window - as a result, your step#1 did nothing to correct my problem (I had already tried that before).

The solution to my problem was simply checking and correcting the following:

" Default settings:

   privacy.trackingprotection.enabled = false
   privacy.trackingprotection.pbmode.enabled = true  "

...as per the post I linked to above ( https://support.mozilla.org/en-US/questions/1092893#answer-803473 ).

Thanks for the info which may help others hoping to solve a similar issue.

Okulungisiwe ngu jenett

more options

I see, tracking protection somehow got enabled in all windows (privacy.trackingprotection.enabled set to true), and returning to the default settings resolved it.

Hmm, if you ever figure out what caused that, let us know.