Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Refresh doesn't work with "reload" tab or F5

  • 7 Antworten
  • 1 hat dieses Problem
  • 2 Aufrufe
  • Letzte Antwort von Terry

more options

Since the newest release, firefox doesn't refresh the images in the website. Every time need to use "CTRL-F5" to refresh the images and the content. It seems don't update the cache.

Since the newest release, firefox doesn't refresh the images in the website. Every time need to use "CTRL-F5" to refresh the images and the content. It seems don't update the cache.

Alle Antworten (7)

more options

Provide steps to replicate the issue an example site. What OS? What Desktop? X11 or Wayland?


Operating System: openSUSE Tumbleweed 20220513 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.2 Kernel Version: 5.17.5-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i7-4810MQ CPU @ 2.80GHz Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4600

more options

Hi, Linux Manjaro with KDE. X11.

more options

I just saw another questions with a similar issue regarding crtl+r and they're working on websites. https://support.mozilla.org/en-US/questions/1377142 What are you doing and can we replicate the steps?

Geändert am von jonzn4SUSE

more options

Thanks, I read the article and it's my same problem. sometimes work and often doesn't work.

more options

Do you use a bookmark that has some GET data appended (?xxx=xxx)?

You can try to remove such trailing GET data

If you use a bookmark to access a specific page then instead navigate to this page starting with the main page or with the sign in page in case there is a problem with this bookmark.

more options

I don't know what is "GET data appended". sorry. The webpage is mine and I access to it directly. the problem happened also with other pages

in randomic way.
more options