I've noticed this issue on a handful of other communities, but making the browser window narrow (mine is 1080x960) makes the .post-layout and #sidebar elements overlap. Maybe something to do with the grid CSS? The #mainbar element seems to be the correct width and changing the .post-layout's overflow-x to auto seems to "fix" it

From retrocomputing:

enter image description here

From this post, because we are meta after all:

enter image description here


  • Google Chrome Version 78.0.3904.108 (Official Build) (64-bit)
  • Ubuntu 18.04.3 LTS
  • 13
    Confirmed, FF mobile (Desktop mode). Started ~20 minutes ago. – Rob Dec 4 '19 at 20:59
  • 5
    Confirmed: Windows 10 (version 1903), monitor resolution 1280×1024 (recommended), Google Chrome the same as OP. – JosefZ Dec 4 '19 at 21:10
  • 1
    It just started happening for me in Firefox for iOS (uses Safari's web engine) here and on Unix & Linux Stack Exchange. – Chai T. Rex Dec 4 '19 at 21:11
  • 2
    Confirmed, Chrome, OS X, 2560 x 1600 – khelwood Dec 4 '19 at 21:11
  • 4
    Thanks for reporting! We've got people looking into it. It sounds like CSS is being temperamental... who would have thought! – Catija Dec 4 '19 at 21:19
  • 2
    @dalearn "end of the day" is relative. We've got people all over the <strike>country</strike> world. It's currently only 1 pm on the west coast. – Catija Dec 4 '19 at 21:22
  • 10
    This isn’t CSS being temperamental… This is just a regular old bug, caused by incorrect styles. It’s wrong in pretty much every browser. You need to set the minimum width. See, e.g., stackoverflow.com/a/43312314 – Cody Gray Dec 4 '19 at 21:28
  • @CodyGray Though you're absolutely right, it seems odd that people are seeing the bug all at once. – connectyourcharger parted ways Dec 4 '19 at 21:33
  • @connectyourcharger from a CSS perspective it's not really a bug, it happens as expected due to a default behavior defined in CSS grid.You simply need to know it to correctly write the CSS. – Temani Afif Dec 4 '19 at 21:35
  • @TemaniAfif Technically you're correct, but it's a bug on the grounds that the style is unintended, and we'll just leave it at that. – connectyourcharger parted ways Dec 4 '19 at 21:41
  • 3
    @connectyourcharger That’s not odd, either. The dev team obviously just deployed an update to their CSS, which contained a bug. I know, it sounds weird, because if you’re like me, you don’t test in production. But, different strokes for different folks. – Cody Gray Dec 4 '19 at 21:42
  • 12
    @CodyGray Who tests in prod on a Wednesday? That's two days early! – manveti Dec 4 '19 at 21:45
  • 2
    @CodyGray They obviously forgot their white chocolate to tie it all together. – connectyourcharger parted ways Dec 4 '19 at 21:48
  • 1
    At least for once it's not just a specific browser, version, os etc. CSS is acting consistently. – memtha Dec 4 '19 at 22:33
  • 2
    This was also reported on meta.stackoverflow and reported there as fixed. – Bryan Krause Dec 5 '19 at 0:19

Answered by @aaron-shekey here:

Thanks for reporting this! We deleted a ton of IE-specific CSS and there was some complicated Less logic causing this bug that we didn’t catch in our local environment. This should now be fixed.

Folks, remember, I’m a person. I’m working hard on improving our codebase every day. Some days there will be visual regressions. I’m sure you’ve shipped some.

Response was written about an hour after I posted my question.


Just for completeness experiencing this on mobile (iPhone XR).

enter image description here

As you can see the question layout is completely cropped to the right and the viewport does not allow you to resize even if you force desktop mode (tested in Google Chrome iOS).

  • 7
    Oh wow it's significantly worse on mobile – GammaGames Dec 4 '19 at 21:40
  • 2
    It’s unusable in it’s current form. – user692942 Dec 4 '19 at 21:42
  • Can confirm it's working as expected now, the question viewport fits correctly. – user692942 Dec 5 '19 at 19:34

I'm facing the same bug. It is a problem for the 9:16 aspect ratio, which is very popular since it's a standard 16:9 monitor turned vertically.

(Sorry if this is more of a comment, I don't have enough rep to comment)

  • 1
    I think you can still upvote the post, even if the points aren't shown publicly it would act as a confirmation – GammaGames Dec 4 '19 at 21:07
  • 4
    @GammaGames You need 15 reputation to upvote, so that's not an option for John. – Glorfindel Dec 4 '19 at 21:10
  • 1
    @Glorfindel: And, now that they have 31 reputation, it is. – Vikki - formerly Sean Dec 4 '19 at 21:37
  • 2
    This does not really answer the question. If you have a different question, you can ask it by clicking Ask Question. You can also add a bounty to draw more attention to this question once you have enough reputation. - From Review – Vikki - formerly Sean Dec 4 '19 at 21:38
  • @Sean thanks to this awesome feature, no one asked for – M-- Dec 4 '19 at 22:22
  • 2
    @Sean Sorry for the commotion, I know it's moot now anyway. But since Meta is the official bug-reporting location and since the only thing a no-rep user can do is post questions and answers, it does put someone new to Meta between a rock and a hard place when it comes to engaging with bug reporting. If I have something small but possibly helpful to add to an existing report - like the aspect ratio it affects - I don't have a good place to put that as a new Meta user. – John Dec 6 '19 at 0:51

I was getting what I think is the same issue at Find minimum number of polygons connecting two points when using Microsoft Edge 44.18362.449.0 on Windows 10 for Workstations:

enter image description here

However, the issue seems to have now been resolved.


Confirmed on Chrome 78 (Windows). I'm also going to add another screenshot I think is a bit of an eyesore:

screenshot of unformatted code blocks

Runnable code blocks don't line-break at all, which creates some very long horizontal scroll distances. Here's a long example from the Sandbox.

  • 1
    Your answer is a few seconds too late, the issue seemed to be fixed now :P – Tom Dec 4 '19 at 22:25
  • @Tom You're kidding. What happened to 6-8 weeks?!?! – connectyourcharger parted ways Dec 4 '19 at 22:26
  • No worries, someone will break it again ;D – Tom Dec 4 '19 at 22:26
  • 1
    @Tom It's been fixed for over a half-hour now for me, I think we just have to wait for caches to expire for the fix to get out there. Especially painful for mobile, they love to hold onto stuff – GammaGames Dec 4 '19 at 22:27
  • @GammaGames -- Not fixed. I just fired up my Macbook a half hour ago and was greeted with this abomination, which wasn't there six hours ago. – barbara beeton Dec 5 '19 at 1:00
  • @barbarabeeton it's being reported as fixed and it is fixed for me, does clearing your cache completely fix it? Maybe their servers aren't all updated yet, though I don't know why it would take so long to spread across – GammaGames Dec 5 '19 at 1:06
  • @GammaGames -- It's still corrupted. Have cleared cache, logged off, shut down, and logged back on, and it's not fixed yet. I first logged on after you reported it "fixed", after having been away for about five hours, when it was still normal. I'll check again in the morning. Thanks. – barbara beeton Dec 5 '19 at 1:53
  • @GammaGames -- I just realized that what I'm seeing is not exactly what is reported, but is a different corruption. There is no overlap, but the up/down arrows and score are, instead of being off to the left-hand side, centered within the text area at the top, occupying about a vertical inch of otherwise empty space. So I guess this is a (botched) consequence of the "fix". I'll see what the situation is in the morning, and if it's still flaky, post a new question. – barbara beeton Dec 5 '19 at 2:02
  • @barbarabeeton is your device updated? I see that if I completely turn off the display: grid rule on the .post-layout element – GammaGames Dec 5 '19 at 2:04
  • @GammaGames -- Unfortunately, my Macbook is too old to be fully updated. I expect to be replacing it soon, so I guess I'll just have to live with what's there. At least, nothing is overprinted or cut off; if the only real loss is wasted space, it's not as bad as it could be. Thanks for hints. – barbara beeton Dec 5 '19 at 2:48
  • 1
    @barbarabeeton I saw the same "up/down arrows" problem like you on the main browser I use (an ancient version of firefox 43.*) which doesn't seem to understand "display: grid", if I change it to "display: inline-flex", it works. you may try update your browser to a version that understand "display: grid" to see whether you can get rid the problem. – achille hui Dec 5 '19 at 3:56

You must log in to answer this question.

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