Mozilla サポートの検索

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.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

Google Reminder About New Terms of Service: Issue Resolved

  • 4 件の返信
  • 1 人がこの問題に困っています
  • 12 回表示
  • 最後の返信者: Buddy2014

more options

When a Google search is done in Firefox, a pop up appears stating 'We're updating our terms of service. Get to know our new terms before they take effect on Mar 31 2020' and there are 'review' and 'got it' options.

I click 'got it' but the pop re-appears the next time the browser is opened and Googled is used again.

Is there a way to permanently block this pop-up from re-appearing?

When a Google search is done in Firefox, a pop up appears stating 'We're updating our terms of service. Get to know our new terms before they take effect on Mar 31 2020' and there are 'review' and 'got it' options. I click 'got it' but the pop re-appears the next time the browser is opened and Googled is used again. Is there a way to permanently block this pop-up from re-appearing?

この投稿は Buddy2014 により に変更されました

すべての返信 (4)

more options

Do you have cookies being deleted when you close firefox?

more options

Eve:

Thank you for the prompt response.

Private Browser mode is turned on.

more options

If you use Private Browsing mode then all the cookies are session cookies that are stored in a separate cookie jar that is purged when you close Firefox or in regular mode when you close all PB mode windows. Each time you open a new PB mode session you will have to confirm the new term as long as Google will show this notice. Unfortunately in Private Browsing mode there is no workaround possible. This will happen with all websites that show a notification and store the aceptance in a cookie or in local storage.

more options

Thank you for clarifying that I will have to confirm the new terms each time a new PB session is opened until Google stops requiring it to be shown.

I figured that there was a simple workaround that I was missing but you have confirmed that I am not missing anything.

Thanks again.