Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Avatar for Username

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Learn More

Toś ta nitka jo se archiwěrowała. Pšosym stajśo nowe pšašanje, joli trjebaśo pomoc.

MacOS Firefox keeps creating a new shortcut in the dock when it is quit

  • 2 wótegronje
  • 0 ma toś ten problem
  • 1 naglěd
  • Slědne wótegrono wót +neo+

+neo+
+neo+
more options

G'day folks,

Just wondering if anyone else is having this curious behavior after updating to FF v112.0 for iOS - every time I quit/ close the FF app, it spawns a new dock shortcut '(even though I already have a valid one from prior use there which works fine!)'.

Is this a bug/ issue that has been noticed/ logged by others as yet?

Thanks!

G'day folks, Just wondering if anyone else is having this curious behavior after updating to FF v112.0 for iOS - every time I quit/ close the FF app, it spawns a new dock shortcut ''''''(even though I already have a valid one from prior use there which works fine!)''''''. Is this a bug/ issue that has been noticed/ logged by others as yet? Thanks!

Wubrane rozwězanje

Hey, thanks for the response - was enabling this toggle, when FF received and applied a minor update; will never know now if this fix worked ;)

Bottom line - problem is solved (y)

Toś to wótegrono w konteksće cytaś 👍 0

Wšykne wótegrona (2)

TyDraniu
TyDraniu
  • Top 10 Contributor
more options

Try to enter 'about:config' in the address bar and switch dom.quotaManager.backgroundTask.enabled to false.


See also:

+neo+
+neo+ Pšašaŕ
more options

Wubrane rozwězanje

Hey, thanks for the response - was enabling this toggle, when FF received and applied a minor update; will never know now if this fix worked ;)

Bottom line - problem is solved (y)