I wanted to know if the comment display problem concerns all TeX.SE users. I see them in a strange position compared to a few days ago.

enter image description here

| |
  • Do you have any active scripts running (through, say, Tampermonkey)? If so, de-activate them and refresh the screen. – Werner Feb 10 at 4:13
  • @Werner I have the same problem but no tampermonkey or similar scripts running. – user194703 Feb 10 at 4:31
  • 3
    This is egreg's fault. He should stop earning reputation and badges. ;) – Werner Feb 10 at 6:21
  • 1
    Yes, Ralph breaks the Internet, aeh, egrep breaks Tex.SX. ;-) – Martin Scharrer Feb 10 at 14:11
  • What browser are you using? If you open developer console (F12 if you're on windows in most browsers) are there any errors reported in the Console? Just FYI: there is done some work on those pages recently: meta.stackoverflow.com/questions/393542/… – rene Feb 10 at 17:42
  • 2
    Maybe this one is a better target: meta.stackexchange.com/questions/342171/… – rene Feb 10 at 17:48
  • @Werner It is our fault. We can just stop upvoting him. – user194703 Feb 10 at 17:52
  • @Werner No, no :-) (aahahahh for the comment on egreg) I have not nothing of this. I have adblock plus, adguard and add-ons to delete the commercial informations. I had always installed these add-ons even before this situation that was regular. – Sebastiano Feb 10 at 18:12
  • @rene I use google chrome with add-ond but before I have not had any problems. I have seen your link and I think just must be a bug. – Sebastiano Feb 10 at 18:14
  • @Schrödinger'scat Ihihihihhihi LOL :-) – Sebastiano Feb 10 at 18:14
  • 1
    That's because the column is too narrow. Pointing this out to the designer of stackexchange should put things in their place. – AndréC Feb 10 at 20:05
  • @AndréC I'm agree with you. – Sebastiano Feb 10 at 20:49
  • 1
    Clearly, it was a wrong adjustment of the width of this column, which has now been corrected. – AndréC Feb 11 at 12:32
  • @AndréC Great Andrè. :-) Now I close my question. Best regards. – Sebastiano Feb 11 at 12:34
  • 4
    I'm voting to close this question because the bug has been solved: see last comment (upvoted). – Sebastiano Feb 11 at 12:35

Browse other questions tagged .