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

Browser view changed to show "mobile" unexpectedly

  • 3 Antworten
  • 3 haben dieses Problem
  • 3 Aufrufe
  • Letzte Antwort von roarhe

more options

Suddenly the browser started to show pages as "mobile view" - page formatting more "text-like", removed backgrounds, - however images shows, but link buttons and other style effects are gone.

I can't find any setting in Tools - Options that seems to solve this problem.

Suddenly the browser started to show pages as "mobile view" - page formatting more "text-like", removed backgrounds, - however images shows, but link buttons and other style effects are gone. I can't find any setting in Tools - Options that seems to solve this problem.

Ausgewählte Lösung

I already had found and tested resetting page style without effect before posting this question; - but the second option in the article, however, "Clear Cached Web Content", solved it. Thank you!

Diese Antwort im Kontext lesen 👍 0

Alle Antworten (3)

more options

try the "reset page style" section from the Websites look wrong or appear differently than they should article

more options

Make sure that you allow pages to choose their colors and that you haven't enabled High Contrast in the Accessibility settings.

  • Tools > Options > Content : Fonts & Colors > Colors : [X] "Allow pages to choose their own colors, instead of my selections above"

Start Firefox in Diagnose Firefox issues using Troubleshoot Mode to check if one of the extensions or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance/Themes).

Geändert am von cor-el

more options

Ausgewählte Lösung

I already had found and tested resetting page style without effect before posting this question; - but the second option in the article, however, "Clear Cached Web Content", solved it. Thank you!