Is it intentional that static navbars now require an additional rule for width?

[thomas-mcdonald]

From the changelog:

Updated .navbar .container to use width: auto; to start and then reset the fixed widths via the #gridSystem mixin (it's a little dirty, but required to avoid adding another class).

However, this means that when using a static navbar with the following code:

<div class="navbar">
  <div class="navbar-inner">
    <div class="container">
      ...
    </div>
  </div>
</div>

this means that the container takes width:auto, ignoring the 940px declaration on .container, and causing all navigation elements to sit at the far left/far right of the navigation.

Of course, this could be the expected behaviour, but it's a breaking change, and not particularly obvious as to the best way to remedy it. .navbar-inner > .container { width:940px; } works nicely, but I am confused as to why fixed navbars have containers with width, while static navbars have containers without width.

[oller]

I've encountered exactly the same issue. The 'width: auto' supercedes the fixed pixel width when the class .navbar-fixed-top is removed to make the navbar static.

[thomas-mcdonald]

Dupe of #2548, my bad.

[sannefoltz]

(added a pull request to fix it)