6

Edit:

This issue looks to be caused by some peculiarity with my StackExchange account, but it happens in both Firefox and Chrome; so something about my account breaks the site, but other (most?) people are unaffected.

Browser OS Extensions Profile Logged-in? Result
Chrome 137 Windows UBlockOrigin Default profile Signed-in as myself Broken
Firefox 139 Windows None Default profile Guest OK
Firefox 139 Windows None Default profile Signed-in as myself Broken
Chrome 137 Windows None Incognito Guest OK

Original post:

I happened across this QA page and noticed the grey boxes and the sidebar looked a bit off...

enter image description here

...then I scrolled down.

enter image description here

Looks like someone published this to production before the weekend, eh?

Edit: Firefox screenshot:

enter image description here

cart StaffMod
1,05710 silver badges13 bronze badges
asked Jun 15 at 11:49
11
  • This might be browser specific. Under Ubuntu 24.04.2 I can't repeat the issue with either (a) Chrome Version 137.0.7151.103 (Official Build) (64-bit) (logged in) (b) Firefox 139.0.1 (64-bit) (not logged in). Commented Jun 15 at 11:56
  • @ChesterGillon One moment, I'll see what I can repro in other browsers now. Commented Jun 15 at 11:57
  • @ChesterGillon I can repro it in Firefox when I'm logged-in as me - but not when a public/guest user. So there's something about my account that breaks it. Commented Jun 15 at 12:05
  • 14
    This is a bug with the experimental comment UI, which is currently an A/B test and thus not visible to everyone. That's why it wasn't consistently reproducible. I've pinged the team working on it and disabled this experiment for now. Commented Jun 15 at 12:32
  • 2
    Please don't use "EDIT"s, edit a post to the best presentation at edit time. Commented Jun 15 at 18:45
  • @balpha Please promote your comment to an answer so I can mark it as accepted - so you get more imaginary internet points. Commented Jun 16 at 0:17
  • @Dai Why don't you quickly write it up as an answer, then you get the (ii) points. Commented Jun 16 at 1:06
  • @W.O. That just wouldn't be fair to balpha Commented Jun 16 at 1:51
  • 2
    @Dai Appreciate it, but since I just disabled the whole new comment UI, I'm expecting someone to re-enable it after fixing it and then respond at that point. Commented Jun 16 at 4:53
  • 6
    Thanks for reporting this, we identified the root cause (with @balpha's help obviously) and pushed a fix Commented Jun 17 at 16:24
  • looks like meta.stackexchange.com/q/396347/997587 Commented Jun 18 at 6:29

0

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.