Bug #2467
closedhttp://www.webtoolkit.eu/widgets/navigation/navigation-bar responsive bug
0%
Description
In Chrome and in Firefox, when I make a browser thin (<700px) and navbar shows data, when I click Help in Menu text of Contents, Index, About is over "Enter search item" edit, it should be hidden (not visible). Link:http://www.webtoolkit.eu/widgets/navigation/navigation-bar
Files
Updated by Josh Lampco almost 11 years ago
- File fix-wt.png fix-wt.png added
- File abs-pos-wt.png abs-pos-wt.png added
I am experiencing this issue also in Google Chrome Version 31.0.1650.57. However, I have come across it while implementing the navigation menu widget within my own development project. I am using Bootstrap V2.2.2 and Wt V 3.3.0.
It seems as though the JavaScript associated with Wt, is adding absolute positioning to the unordered list associated with the class "dropdown-menu". When I change the positioning to static, as it is in the bootstrap-responsive.css v2.2.2, and also delete the following style
.nav-collapse .dropdown-menu {
display: block !important;
}
which is found in wt.css, I see that the layout is corrected.
I have attached screenshots of the bug as seen here. In the developer tools console at the bottom of the attached images, I have shown what I changed.
Updated by Josh Lampco almost 11 years ago
After further testing, simply adding static positioning will not fix the problem. A media query will need to be used as the menu needs static positioning only when the browser window is less than 979px.
@media (max-width: 979px) {
.nav-collapse .dropdown-menu {
position: static !important;
}
}
Keep in mind that at this point my solution is very "hacky". Hopefully, someone can come up with a better solution that does not involve media queries and overwriting the JavaScript.
Updated by Koen Deforche about 10 years ago
- Status changed from New to InProgress
- Assignee set to Koen Deforche
- Target version set to 3.3.4
Updated by Koen Deforche about 10 years ago
- Status changed from InProgress to Resolved
This problem appears to have been solved already.
Updated by Koen Deforche over 9 years ago
- Status changed from Resolved to Closed