Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

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

Èròjà atẹ̀lélànà yii ni a ti fi pamọ́ fọ́jọ́ pípẹ́. Jọ̀wọ́ béèrè ìbéèrè titun bí o bá nílò ìrànwọ́.

All shortcut tiles on new tab page have turned white and no longer do anything

  • 1 èsì
  • 1 ní ìṣòro yìí
  • 25 views
  • Èsì tí ó kẹ́hìn lọ́wọ́ mattsg

more options

On my new tab page, I had 8 shortcut tiles configured with custom icons for quick access to those sites. Now all those icons are default white squares that don't do anything when clicked.

Also, if I try to edit one and recreate what it was previously, it appears to accept my input but then nothing happens when I click the shortcut. If I edit that shortcut again, the stuff I entered is gone.

So basically, the shortcut tile feature on the new tab page is non-functional for me. (This is on the current version of Firefox (97.0.1) for Windows 10 (version 2004, build 19041.1415).

On my new tab page, I had 8 shortcut tiles configured with custom icons for quick access to those sites. Now all those icons are default white squares that don't do anything when clicked. Also, if I try to edit one and recreate what it was previously, it appears to accept my input but then nothing happens when I click the shortcut. If I edit that shortcut again, the stuff I entered is gone. So basically, the shortcut tile feature on the new tab page is non-functional for me. (This is on the current version of Firefox (97.0.1) for Windows 10 (version 2004, build 19041.1415).

Ọ̀nà àbáyọ tí a yàn

Firefox updated today and, as if by magic, the problem fixed itself.

No, I don't get it either.

Ka ìdáhùn ni ìṣètò kíkà 👍 0

All Replies (1)

more options

Ọ̀nà àbáyọ Tí a Yàn

Firefox updated today and, as if by magic, the problem fixed itself.

No, I don't get it either.