This is not a post about the positives or negatives of the new navbar color at the top of all StackExchange sites, but it does have to do indirectly with the navbar color.  Now that the expandable search box has gone away, an interesting quirk occurs when you have your browser narrow enough to cause horizontal scrolling to kick in.     Exhibit A:  the browser scrollbar has activated because user has reduced the width to a size roughly less than the 980px width of the #content div container.     Exhibit B: the search box looks ok, right?     Exhibit C: well, maybe not...because what is the search box doing there, partly in a black background, and partly in a white background?     To conclude: the top navbar appeareance should persist across the full width of the browser when the browser size is reduced, even if the search box in the right corner makes that more challenging.
44881
Update  A month Several months later, a new top bar, and the bug still exists. An answer has already been posted that would fix the bug, so is this something that the dev team plans on fixing?  There are also a host of other problems caused by this, especially on the  and . Again, this would be fixed with  html{min-width:1000px;}   There is a slight bug with small windows on both the new meta and main site(s)?, shown here. The problem is that the top bar coloring doesn't stretch across when you resize and scroll left or right.        On Meta, when a horizontal scroll bar is needed, the black background will only be as wide as the width of the viewport, but when you scroll the coloring will not shift.  To reproduce:   Make screen as large as possible, or wait until the menu bar starts expanding Make it smaller and smaller until horizontal scrollbar appears, then scroll left and right.
74941
When I hover over featured tab, both on the front page and in questions, the questions move down by one pixel. Here's a small screen capture demonstrating the issue:        I see it in Chrome 34 and Opera 20, but I don't see it on IE11 or Firefox 28.
106757
In thinking and reasoning about the new question navigation bar and trying to figure out where unnecessary and necessary redundancies are and what could be improved, I more often than not stumble across the problem that I don't really know what all those different options actually do, and neither of the two iterations of that official announcement question seems to completely explain it. I feel that any further question I'd ask might simply be an XY problem of not knowing what I want to improve at all. It might be clear to people deeply acquainted with the old navigation bar already what e.g. "recommended" actually means, but there are also other sub-options that seem to .  So hands down, what are the exact technical criteria (i.e. votes/answers/views whatever) that all the different tabs and their filtering/showing sub-options employ for filtering questions? I know what the tag filters do, or what the time filters in the "popular" tabs do, but especially some "show" options are a bit unclear to me, and others might be clear but I'd still like to have it canonically answered to be sure. In particular I'm having problems grasping the following options:  "new" tab   show: all vs show: recommended - That doesn't seem to filter only my favourite tags (for which there's a separate filter anyway), so what is recommended at all?   "popular" tab   sort: hot - Does this use the "arbitrary hotness points" of the HNQ or another hotness formula, or even other criteria in addition?   "need answer" tab   show: need answer vs show: no answer - I figure those are the good old "no accepted/upvoted answers" vs "no answer at all" options. But do they use additional criteria? I'm asking because some of the  in the old design had the unexpected behaviour of excluding negatively voted questions. show: all - What does this actually show? It seems to include questions with accepted answers, but how does it then differentiate from the show: all view in the "new" tab? Or maybe this even is absolutely intentional redundancy for easier usability?
105195
I am using a default font size of 26px and stackoverflow's layout seems to not work well with such a large sizes.  The most important issue is that many inputs tend to overflow and partially get hidden below side text. This includes one with login, ‘Title’ and — the most important issue — the editor, which makes writing posts a little painful.  Another important one is that sometimes 'search' field doesn't fit in topbar and jumps lower, being partially hidden by logo. I met that issue on stackoverflow itself only while serverfault &amp; meta display fine (but that may be related to rep or sth).  There's one minor issue too — navbar is too narrow and ‘Ask Question’ jumps below — but this one looks quite nice (maybe it's even intended?).  Screenshot: (click to enlarge)
9121
I have noticed that while asking questions and scrolling to the bottom of the page, the right sidebar containing recent questions covers the footer partially. Also, a part of it goes beyond the browser's boundary. It may not be a big problem but it still doesn't look good.    This also happens on the  page
120877
There is an alignment issue in the stackexchange.com search page .  The bottom bar is missing in the search input box.  Sample URL:   Screen shot for reference:    Firefox version: 54.0b8 (32-bit) OS Version: Windows 10 Pro  Also happens with Chrome latest version.
8221
Stack Overflow seems to be having some CSS issues right now. At first, it presented as CSS disappearing when refreshing in Firefox (though hitting Enter from the address bar seemed to restore it - I'm thinking that's a cache issue though). I loaded my blank Firefox profile and discovered CSS wasn't rendering on Stack Overflow at all (Meta seems fine; haven't checked other SE sites).  I've since checked the site in Chrome and Opera, and can repro in both.
22413
There is a little bug that becomes visible when a page contains realtime-post-deleted-notification banners (that's the CSS classname of these red banners appearing on answers which just got deleted, see screenshot below) and you try to open the flag dialogue above them:    Obviously, the dialogue appears below the banners, which it clearly should not do. It also has no input focus, trying to interact with the dialogue fails and either closes it (clicking outside of the red banners) or reloads the page (clicking on the red banners).  The cause for this is simply the z-index ordering in the site's CSS. Relevant CSS snippets:  .realtime-post-deleted-notification {     position: absolute;     text-align: center;     z-index: 100; }  .popup {     display: none;     padding: 15px;     position: absolute;     z-index: 10; }   So the fix for this minor bug would probably be to raise the z-index of the popup class to something greater than 100.
119506
I've seen this question already:   I remember that Chrome used to do this if you go to the History view and enter a query in the search box there.  However, it's not working for me anymore. I can't find anything now!  Did Chrome stopped doing this? Am I missing something? Do I have to enable/disable something?
24124
Sometimes, when you create a question which returns a lot of similar questions, it makes the height of the floating "Similiar Questions" box too big to fit on the page. As a result, it blocks some of the footer on the right hand side. It's actually doing it as I type this question.  I think a max height based on the view port - footerHeight should fix it.
10943
It would be nice to support showing images in their original size when they where automatically resized because they are too big to fit in a question or answer ().  I envision it just like in blogs or facebook: You can click on the image and it is shown in its original size in an overlay.
60175
I've been running into this lately.  The scroll-bar gets stuck and makes it difficult to read the text.  I'm running Chrome Version 56.0.2924.87 (64-bit) on macos.
78990
It's just a minor CSS issue. See the following gif:
9370
Update:  Thanks for all the feedback and bug reports! I am locking this thread so people don't keep answering it when we no longer monitor it.  If you see a bug or want to raise a feature request, please do so in the usual manner, as a new question.    Some of you may have noticed that  the  and  pages that we have been talking about for a while now on .  Most? Well, yes, the new design is dependent on a SE network-wide update (a new base css framework) that the design team have been working on. This is an ongoing effort and we will be launching the new pages as sites are moved to the new design.  You've all been hugely helpful already - much of what we love most in here came from  and  you gave us on Meta.     But it's possible that it's not quite perfect yet. If you find any bugs and have any feedback to give, please post these as answers to this post.  Just post one issue per answer - that would help us focus on specific items one at a time.
67596
So when you use the comment shortcut C, you get the comment box appearing. However, you will get a weird black box.  Here's a picture of before:           And afterwards:           And after reloading, it disappears! This seems weird.  And after looking at the HTML, this seems to be the problem:  &lt;div data-questionid="260187" id="question" class="question keyboard-selected"&gt;   After removing the class attribute, the box goes away.
80777
Each beta site has such box in the right sidebar of the homepage:    Expected behavior when clicking &quot;stack exchange&quot; is the list of sites displayed and auto scrolled to the relevant site, or if grid view then the relevant site will auto expand itself. Observed behavior: it's just showing the list of sites and that's it. The link raw URL is something like http://stackexchange.com/sites?expand=true#movies so it looks like it used to work before and got broken at some point. (no named anchors anymore)
65449
I tend to keep my Chrome zoomed to 90% (it gives me more real estate on my work monitor. When I do the layout on , it breaks (see the image below).      `