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!

Ovo će web mjesto raditi na ograničen način, dok obavljamo održavanje stranice. Ako neki članak ne riješi tvoj problem i ako želiš postaviti pitanje, naša zajednica za podršku spremna je pomoći na Twitteru @FirefoxSupport i na Redditu /r/firefox.

Avatar for Username

Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

Ova tema je arhivirana. Postavi novo pitanje ako trebaš pomoć.

Site Information drop-down is corrupted

  • 2 odgovora
  • 1 ima ovaj problem
  • 11 prikaza
  • Posljednji odgovor od sam

sam
sam
more options

The "Site information" drop down on the far left of the address bar is corrupted, showing an infinitely repeating pattern of icons. See attached picture for example.

The "Site information" drop down on the far left of the address bar is corrupted, showing an infinitely repeating pattern of icons. See attached picture for example.
Priložene slike ekrana

Izabrano rješenje

Hi cormac, that is a known issue with ShadowFox.

As a temporary (?) workaround, you can edit out its rules related to the Site Identity Area. There are steps for that in this issue:

https://github.com/overdodactyl/ShadowFox/issues/284

Does that work for you?

Pročitaj ovaj odgovor u kontekstu 👍 1

Svi odgovori (2)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 10 Contributor
more options

Odabrano rješenje

Hi cormac, that is a known issue with ShadowFox.

As a temporary (?) workaround, you can edit out its rules related to the Site Identity Area. There are steps for that in this issue:

https://github.com/overdodactyl/ShadowFox/issues/284

Does that work for you?

sam
sam Vlasnik pitanja
more options

I completely forgot I even had ShadowFox installed. There is a pull request with a fix, and using that solved the issue. Thank you for the help!