Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed Navbar resizes with navbar-right elements if type=password input exists on the page (Chrome only) #13892

Closed
jordanfloyd opened this issue Jun 22, 2014 · 9 comments · Fixed by #14037

Comments

@jordanfloyd
Copy link

This bug exists only in google chrome, both in Windows and in OSX
If a fixed navbar is used with navbar-right elements, such as a button, and input type=password is used inside a form anywhere on the page, when the page is reloaded the navbar pushes elements to a new row, making it too tall.

http://jsbin.com/daxopusa/3/ - Reload the page after navigating to it.

http://jsbin.com/daxopusa/3/edit - If you remove type=password from the input, the issue disappears.

@twbs-lmvtfy
Copy link

Hi @jordanfloyd!

You appear to have posted a live example (http://jsbin.com/daxopusa/1), which is always a good first step.
However, according to the HTML5 validator, your example has some validation errors, which might be causing your issue:

  • line 119, column 7: End tag for body seen, but there were unclosed elements.
  • line 66, column 27: Unclosed element div.

You'll need to fix these errors and post a revised example before we can proceed further.
Thanks!

(Please note that this is a fully automated comment.)

@jordanfloyd
Copy link
Author

updated example with valid HTML

http://jsbin.com/daxopusa/3/

@cvrebert cvrebert added the css label Jun 22, 2014
@cvrebert cvrebert added this to the v3.2.1 milestone Jun 22, 2014
@dmolineus
Copy link

confirmed on Linux (Chrome) as well.

@cvrebert
Copy link
Collaborator

Bizarre. Confirmed on OS X Chrome.
Resizing the window until the navbar collapses, and then resizing it again until it uncollapses, also seems to cause the rendering to fix itself.

@cvrebert
Copy link
Collaborator

cvrebert commented Jul 3, 2014

@mdo I guess we should file a Chrome bug about this?

@mdo
Copy link
Member

mdo commented Jul 3, 2014

@cvrebert Yeah, probably. Sorry, I haven't looked into this one extensively yet.

@cvrebert
Copy link
Collaborator

cvrebert commented Jul 3, 2014

Relatively minimized (HTML-wise) testcase: http://jsbin.com/fehoqapu/1

@cvrebert
Copy link
Collaborator

cvrebert commented Jul 4, 2014

This is presumably caused by https://code.google.com/p/chromium/issues/detail?id=377346

cvrebert added a commit that referenced this issue Jul 4, 2014
cvrebert added a commit that referenced this issue Jul 4, 2014
Add Wall of Browser Bugs entry for #13892
@cvrebert
Copy link
Collaborator

cvrebert commented Jan 9, 2015

Chrome bug is claimed to have been fixed in Canary (v41): https://code.google.com/p/chromium/issues/detail?id=377346#c6

cvrebert added a commit that referenced this issue Jan 9, 2015
So remove its entry from the Wall of Browser Bugs.
Refs #13892, #14037

[skip sauce]
cvrebert added a commit that referenced this issue Jan 9, 2015
Remove #13892's entry from the Wall of Browser Bugs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants