Avatar for Username

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Dieses Thema wurde archiviert. Bitte stellen Sie eine neue Frage, wenn Sie Hilfe benötigen.

Firefox Nightly: new tab shows "most visited sites", even when this is disabled in Settings

  • 2 Antworten
  • 1 hat dieses Problem
  • 1 Aufruf
  • Letzte Antwort von pg_78

pg_78
pg_78
more options

In the latest (1/27) version of Firefox Nightly, a newly created tab always shows the "most visited sites", even when this feature has been switched off in Settings >> Customise >> Home.

On all previous versions, this worked correctly.

What's the best way to raise this with the developers? GitHub and/or Bugzilla?

In the latest (1/27) version of Firefox Nightly, a newly created tab always shows the "most visited sites", even when this feature has been switched off in Settings >> Customise >> Home. On all previous versions, this worked correctly. What's the best way to raise this with the developers? GitHub and/or Bugzilla?

Ausgewählte Lösung

Hi

Thank you for using Firefox for Android Nightly and helping make the next version of Firefox more awesome.

If you wish to file a bug, you can do so at:

https://github.com/mozilla-mobile/fenix/issues/new?assignees=&labels=%F0%9F%90%9E+bug&template=---bug-report.md&title=%5BBug%5D

Diese Antwort im Kontext lesen 👍 1

Alle Antworten (2)

Paul
Paul
  • Top 25 Contributor
  • Moderator
more options

Ausgewählte Lösung

Hi

Thank you for using Firefox for Android Nightly and helping make the next version of Firefox more awesome.

If you wish to file a bug, you can do so at:

https://github.com/mozilla-mobile/fenix/issues/new?assignees=&labels=%F0%9F%90%9E+bug&template=---bug-report.md&title=%5BBug%5D

pg_78
pg_78 Fragesteller
more options

Many thanks Seburo. As it turned out, this was fixed within a couple of days and before I got round to logging it! :-)