Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

Selecting private browsing mode has no visual indication

  • 3 отговора
  • 7 имат този проблем
  • 23 изгледи
  • Последен отговор от cinimodvii

more options

When I select on my Mac OS, preferences, privacy then check "Always use private browsing mode". When firefox is started it does not show any indication I am using privacy browsing. I think it should show the mask symbol in the corner as it Firefox does when you don't have privacy settings set and manually select private browsing.

When I select on my Mac OS, preferences, privacy then check "Always use private browsing mode". When firefox is started it does not show any indication I am using privacy browsing. I think it should show the mask symbol in the corner as it Firefox does when you don't have privacy settings set and manually select private browsing.

Избрано решение

You do not get the purple mask when you are in permanent PB mode because all windows are private by default. You only see the mask when you open a New Private Window in normal mode.

You can use an extension to get Private Browsing mode support per tab.

Прочетете този отговор в контекста 👍 1

Всички отговори (3)

more options

Избрано решение

You do not get the purple mask when you are in permanent PB mode because all windows are private by default. You only see the mask when you open a New Private Window in normal mode.

You can use an extension to get Private Browsing mode support per tab.

more options

I understand. I think a visual confirmation would be appropriate to confirming the state of Firefox.

more options

mace2 said

I understand. I think a visual confirmation would be appropriate to confirming the state of Firefox.

This is a major cock-up on the part of the developers. I won't be using Firefox until they have fixed this issue.