We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Search Support

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.

Learn More

This thread was archived. Please ask a new question if you need help.

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

  • 2 replies
  • 1 has this problem
  • 1 view
  • Last reply by 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?

Chosen solution

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

Read this answer in context 👍 1

All Replies (2)

Paul
Paul
  • Top 25 Contributor
  • Moderator
more options

Chosen Solution

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 Question owner
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! :-)