Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Avatar for Username

ค้นหาฝ่ายสนับสนุน

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.

เรียนรู้เพิ่มเติม

หัวข้อนี้ถูกเก็บถาวรแล้ว โปรดถามคำถามใหม่หากคุณต้องการความช่วยเหลือ

No "Save" button for Google Search settings (Android 65.0.1)

  • 2 การตอบกลับ
  • 1 คนมีปัญหานี้
  • 3 ครั้งที่ดู
  • ตอบกลับล่าสุดโดย Mildred PC

Mildred PC
Mildred PC
more options

Not able to save Google search settings. There is no "Save" button displayed when I access the Google search settings page from the google.co.uk homepage. Works fine in Chrome but not in Firefox. Why Firefox doesn't display the saved settings I change when I save them in Chrome I have no idea! Signed in to Google on both Chrome &Firefox. Completely stumped and frustrated. Any help?

Not able to save Google search settings. There is no "Save" button displayed when I access the Google search settings page from the google.co.uk homepage. Works fine in Chrome but not in Firefox. Why Firefox doesn't display the saved settings I change when I save them in Chrome I have no idea! Signed in to Google on both Chrome &Firefox. Completely stumped and frustrated. Any help?

วิธีแก้ปัญหาที่เลือก

Google doesn't provide the Save button on the site's version they send to Firefox. You have to install this addon.

อ่านคำตอบนี้ในบริบท 👍 0

การตอบกลับทั้งหมด (2)

TyDraniu
TyDraniu
  • Top 25 Contributor
more options

วิธีแก้ปัญหาที่เลือก

Google doesn't provide the Save button on the site's version they send to Firefox. You have to install this addon.

Mildred PC
Mildred PC เจ้าของคำถาม
more options

Thanks for the reply. Found a workaround. Requested the "desktop" version, changed the settings and it saved them OK. Surely Google is acting unlawfully by restricting functionality like this! Anyway, all's good now - thanks.