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!

当サイトはユーザー体験を改善するためのメンテナンスを実施中に機能が制限される予定です。記事を読んでもあなたの問題が解決せず質問をしたい場合は、Twitter の @FirefoxSupport、Reddit の /r/firefox で、サポートコミュニティが皆さんを助けようと待機しています。

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.

詳しく学ぶ

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

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

  • 2 件の返信
  • 1 人がこの問題に困っています
  • 1 回表示
  • 最後の返信者: 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?

選ばれた解決策

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

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

すべての返信 (2)

more options

選ばれた解決策

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

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