-
-
Notifications
You must be signed in to change notification settings - Fork 79k
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
.dropdown-menu in .navbar does not appear in Android Chrome #2767
Comments
@Darcnes Does this happen in the docs? |
@markdotto Afaik docs does not have an example of a fixed-top navbar with a dropdown, though in the components page, if you scroll down so that the subnav sticks to the top, it also exhibits this behavior. When Buttons or Navigation is clicked no dropdown appears. |
@Darcnes go to the Javascript plugins page, there's examples on there. |
It's worth noting that both the example navbar and the subnav when not docked display their menus appropriately. I also noticed that if I tapped on the subnav menu while it was docked (and nothing appeared) that if I scrolled to the top of the page where the subnav un-docked, the menu would be open and visible once it was free floating again. |
@add1ct3dd Thanks. However, the free-floating navbars are not affected by this issue. Only once a navbar is docked does it not display its dropdown menus. |
http://dl.dropbox.com/u/11160803/Screenshot_2012-03-27-09-31-59.png Here you can see the transition, the 'active' class is still in effect, but the menu disappears as soon as it docks. |
Ok I've tested my website that uses these and they work fine on my Motorola Xoom (ICS), what Android build are you running? To confirm, my navbar is fixed at the top. I'd upload a screenshot but not sure what my default key is to take one :) |
Transformer Prime ICS 4.0.3 .. and just to be sure, you tried this in the Chrome browser? The stock browser appears to render just fine. Edit: I've also tested this on my Atrix running a CM9 Kang, again stock browser no issues, Chrome browser no dropdowns. As for screenshots, it depends on which ICS ROM you're running, it's not a native ICS feature. The EOS ROM at XDA is very well done however and has screenshot baked in. (I used EOS since the day I unlocked my 4G Xoom til the day I sold it for the TF Prime.) Otherwise you're left with an app like Screenshot Grabber or Screenshot ER. |
I just noticed I was running an old Chrome Beta version, updated and now I get the same error! fyi, EOS Nightly build (84), what's your default screenshot key? :) |
So it sounds like something they did in the update is what broke the functionality. As for the screenshot key, you have to enable it in the settings. It's either under the EOS specific settings or Display. Here's the link I posted around the same time I posted here on the off chance is was browser related instead: |
So are you guys thinking this is browser related then? |
That appears to be the case, being the only browser with the issue and only
|
Gotcha. If you guys find anything else out, please don't hesitate to open a new issue if it can be fixed. Thanks for all the debugging and research :). |
As these screenshots show, the dropdown menu in a top-fixed navbar when clicked is not visible. It appears to be either not be rendering or is hidden behind the element below it.
I used three examples from the builtwithbootstrap.com site to demonstrate this. The first screenshot is one page without anything clicked, the second is the menu in the top right-hand corner clicked (note the small white notch in the black background of the navbar below the dropdown button), each of the last two show this behavior in other websites.
Not sure if this is an issue with Bootstrap or with the Android flavor of Chrome (it's worth noting that the stock browser renders it just fine..). But it is reproducible.
http://dl.dropbox.com/u/11160803/Screenshot_2012-03-23-08-59-33.png
http://dl.dropbox.com/u/11160803/Screenshot_2012-03-23-08-59-38.png
http://dl.dropbox.com/u/11160803/Screenshot_2012-03-23-08-59-44.png
http://dl.dropbox.com/u/11160803/Screenshot_2012-03-23-08-59-49.png
The text was updated successfully, but these errors were encountered: