Windows 10 reached EOS (end of support) on October 14, 2025. For more information, see this article.

Mozilla サポートの検索

サポート詐欺に注意してください。 私たちはあなたに通話やショートメッセージの送信、個人情報の共有を求めることはありません。疑わしい行為を見つけたら「迷惑行為を報告」からご報告ください。

詳しく学ぶ

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

Setting preferences in Google search ... I can't get the "Open search results in a new browser window." setting to stick. It seems to revert randomly to the unset state. Other settings stick fine. Any ideas?

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

Cookies settings: tracking not selected; Use custom setting for history selected; permanent browsing not selected; remember download not selected; remember search and form selected; accept cookies and accept 3rd party selected; keep until expired ...


Clearing history settings: History ... browsing, download, active and cache selected forms and search, cookies not selected

Data ... offline and site pref selected ; saved pwds not selected

Cookies settings: tracking not selected; Use custom setting for history selected; permanent browsing not selected; remember download not selected; remember search and form selected; accept cookies and accept 3rd party selected; keep until expired ... Clearing history settings: History ... browsing, download, active and cache selected forms and search, cookies not selected Data ... offline and site pref selected ; saved pwds not selected

選ばれた解決策

It's not an issue of whether the user saves or does not save the preferences, there are several factors that could be causing this. The KB link I posted above explains the issue & solution in detail.

この回答をすべて読む 👍 0

すべての返信 (4)

How to fix preferences that won't save

This should help you out considerably. I also previously experienced this issue & other preferences not saving.

I always save my preferences when I exit from the search setting page ... the problem is deeper than that.

選ばれた解決策

It's not an issue of whether the user saves or does not save the preferences, there are several factors that could be causing this. The KB link I posted above explains the issue & solution in detail.

Thanks ... in my impatience, I had neglected to go out to the link. I fixed the problem. I appreciate YOUR patience with me!!!