4

As of today comments do not render MathJax and remaining text. It only flashes the underlying LaTeX, but renders an empty space. Noticed on MSE and MO, for example here one comment now simply reads: "@Eric Write – Aweygan Jan 26 at 14:08 ".

Have tried different MathJax renderers or other MathJax context menu settings.

The problem appears on Windows 7 32bit and Firefox ESR (with a clean profile too). Works normal on Chrome and the new Firefox Quantum.

UPDATE: Broken on Tor Browser 7.0.2 (based on Firefox 52.2.0). But works on PaleMoon 27.7.1! Broken on Basilisk web browser.

Improve this question
3
  • 1
    ESR is not officially supported.
    – Sonic the Anonymous Hedgehog
    Commented Feb 1, 2018 at 12:05
  • 1
    There have been patches out earlier today: meta.stackexchange.com/a/306503/158100 this can be yet another regression.
    – rene Mod
    Commented Feb 1, 2018 at 12:06
  • 1
    Sonic and @rene - thanks for instant replies. I'm afraid ESR will continue to be widely used for a while and is occasionally updated: mine is 52.6.0.
    – user612313
    Commented Feb 1, 2018 at 12:22

2 Answers 2

Reset to default
4

As noted in the comments to the post Comment timestamp is not showing in Firefox ESR, there are two workarounds for now for Firefox ESR 52.6.0.

  • Click on "show xx more comments" (if this is present).
  • Otherwise, open and close the Web Developer Inspector panel (Cntrl+Shift+C).

Hopefully, these will be needed only temporarily.

Update: It seems that the patch from almost two years ago is no longer working, or has been deleted. But both of these workarounds still work (tested on ESR 52.9.0 32-bit).

Improve this answer
3
  • 1
    Both workarounds work! Thank you, Joseph. Works on MO also. Let's wait and see if it gets fixed and then we can close this question.
    – user612313
    Commented Feb 1, 2018 at 15:56
  • 1
    Update: The developer says he/she hopes to have a quick patch ready tomorrow, link.
    – Joseph Quinsey
    Commented Feb 1, 2018 at 20:04
  • Update 2: It seems that the patch from almost two years ago is no longer working, or has been deleted. But both of these two workarounds still work. (Tested on ESR 52.9.0.) This comment was added Dec 12, 2019, which I note here because if you are reading this, you likely cannot see the SE date :(.
    – Joseph Quinsey
    Commented Dec 11, 2019 at 15:50
1

Works fine now, see my other answer.

Improve this answer
1
  • 1
    Yes, thank you so much! And sorry for the nuisance of having to support an older browser.
    – user612313
    Commented Feb 2, 2018 at 12:42

You must log in to answer this question.

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