7

Since today, suddenly code no longer displays for me:

Screenshot showing empty code blocks

The same happens for in-line code, also that in comments. However, I can select the code:

Enter image description here

and copy-paste it to a text editor. Is this a new bug?

I'm running Windows 11 with Firefox 103.0.2 (64-bit) with uBlock Origin, Adblock Ultimate, Privacy Badger and Tampermonkey.

Opening the same page in a fresh, incognito browser window without add-ins does indeed display the code. Could this be related to the earlier issue today and be fixed by simply waiting for caching to catch up?

Improve this question
11
  • 3
    No repro with Chrome, try clearing cache, removing extensions, etc.
    – Shadow Wizard
    Commented Aug 25, 2022 at 8:10
  • 1
    No repro on FireFox 103.0.2 (64-bit) on macos 12.5 either.
    – Martijn Pieters
    Commented Aug 25, 2022 at 8:22
  • Regarding cache, in Chrome you can force it to clear in several ways: 1) Reload with CTRL+F5, 2) Open dev console, go to Network tab, tick "Disable cache" checkbox and reload, and 3) Clearing all cache from Settings. Pretty sure Firefox also have at least part of those.
    – Shadow Wizard
    Commented Aug 25, 2022 at 8:50
  • 4
    @ShadowTheKidWizard jup, clearing cache through settings did the trick. CTRL-F5 did not btb.
    – Adriaan
    Commented Aug 25, 2022 at 8:53
  • 2
    Worth self answer then, IMO.
    – Shadow Wizard
    Commented Aug 25, 2022 at 9:16
  • 1
    Heh, just thought of something, the broken JS yesterday was an earthquake, and this one here is an aftershock. ;-)
    – Shadow Wizard
    Commented Aug 25, 2022 at 9:38
  • Does this answer your question? JavaScript is broken
    – Spevacus Mod
    Commented Aug 25, 2022 at 14:00
  • 1
    Wrong close reason, no changes were made to the system. Proper action would be marking it as status-norepro as the bug already fixed, and it's something local for some users with aggressive caching.
    – Shadow Wizard
    Commented Aug 25, 2022 at 14:22
  • @ShadowTheKidWizard the dupe would fit though, as the answer there answers this question as well (at least, that's what I think. A dev would need to confirm that)
    – Adriaan
    Commented Aug 25, 2022 at 14:30
  • The dupe explains why it was broken in the first place, but doesn't mention you have to clear cache.
    – Shadow Wizard
    Commented Aug 25, 2022 at 14:32
  • For future reference regarding refreshes, a hard reload in Chrome (Ctrl + F5 or Ctrl + Shift + R) makes a fresh request for the page without cached data, but doesn't necessarily dump any other cache for the page. "Empty Cache and Hard Reload" in Chrome does, however, which can be accessed by opening dev tools and then right clicking the refresh button. A more thorough explanation.
    – zcoop98
    Commented Aug 25, 2022 at 15:59

1 Answer 1

Reset to default
7

It turns out the problem was broken JS stored in the browser's local cache. This issue was possibly related to this quick-fix earlier today.

These are the steps I took to clear the cache (Firefox):

  1. Go to Settings
  2. Privacy & Security
  3. Cookies and Site Data
  4. Clear Data
  5. Cached Web Content

Note, Ctrl + F5 didn't help unfortunately.

Improve this answer

Not the answer you're looking for? Browse other questions tagged .