Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

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.