Closed (fixed)
Project:
Navbar
Version:
7.x-1.x-dev
Component:
User interface
Priority:
Major
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
26 Aug 2012 at 19:09 UTC
Updated:
3 Dec 2013 at 21:40 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
cashwilliams commentedI see this as a big blocker. First thing I did when demoing this to a client was setup a clean install with the client's choice of theme (bootstrap). Boom, sad panda.
Comment #2
hass commented#1916300: Conflict with Mobile friendly navigation toolbar module has been marked as duplicate.
Comment #3
jessebeach commentedUgh. Sad panda indeed.
https://github.com/twitter/bootstrap/blob/master/less/navbar.less
What if we changed the class on the wrapping element from
.navbarto.drupal-navbar?I'm attaching a patch. CashWilliams and andregriffin, can you test this with Bootstrap and see if it resolves the issue?
This is probably a good candidate for forward-porting to D8 as well.
Comment #4
hass commentednavbar-menushould be safe and not so drupal branded? I like to see this fixed too, but the naming sound not optimal to me.Comment #5
andregriffin commentedAlmost. There were also some conflicts with the
.iconclass, but adding some "auto" values for width and height, andbackground: none;seemed to fix everything. Also pushing out a commit soon for Bootstrap to prevent our theme_menu_link function from doing dropdown-menu stuff on the management menu.Comment #6
caschbre commentedI recently opened a new issue that may be a dupe of this one. Can someone confirm?
#1955912: Conflict with FontAwesome
Comment #7
caschbre commentedI've tested patch #5 against my custom theme that includes the fontawesome css and after an initial run through it's looking good.
Comment #8
jessebeach commentedThanks andregriffin for the patch and caschbre for testing. There were a few holes in the RTL files. I've filled them in. The patch in #5 didn't apply cleanly because of changes to Navbar since it was created, so I had to guess at how to apply the changes. Please verify that 3rd party themes are working with the development version of Navbar. If not, a further patch or screenshots will help us get it fixed.
Comment #9
shadcn commentedPatch in #8 works well. Super thanks.
See my comment here #1955912: Conflict with FontAwesome for icon classes and fontawesome support.
Thanks
Comment #10
hass commentedShouldn't this not wait for the backport #1938044: Prefix all toolbar classes to prevent theme clashes?
Comment #11
busla commentedUpdated navbar to latest dev in my Spark install and it worked fine execpt for the Responsive Preview dropdown. See screenie.
Comment #12
hass commented#1938044: Prefix all toolbar classes to prevent theme clashes has been committed. We can follow up now...
Comment #13
dsnopekI'm going to make an attempt at the backport from Drupal 8 toolbar... I'll post a patch soon.
Comment #14
dsnopekAttached is a patch against the Navbar 7.x-1.x branch! It was made by walking through the patch from #1938044: Prefix all toolbar classes to prevent theme clashes line-by-line and making the equivalent changes in the navbar module. I tested manually and everything seems to be working correctly. Please let me know what you think!
Comment #15
dsnopekOne random note: it appears as though Panopoly is going to release their 1.0-rc5 soon with Navbar 1.0-alpha10. However, without these changes, that won't work with Open Atrium 2.0 (based on Panopoly) because it uses Bootstrap in it's default theme. If we can get these changes in and a Navbar 1.0-alpha11 made quickly, we could possibly avoid some complications for Open Atrium 2.0.
Here is the issue on the Panopoly issue queue: #1971292: Minor fixes for Navbar module in panopoly_admin.make
Anyway, I'm not trying to rush you. :-) If some patches need to be thrown in some make files for other distributions, so be it. I just thought I'd let you in on some related things happening in other projects.
Comment #16
dsnopekI just realized that I skipped a patch that was applied to Drupal 8 Toolbar before the one I backported. I've created a Task to backport it too: #2050699: Backport "Reduce dependency on JavaScript" from Drupal 8 toolbar
Comment #17
shadcn commentedPatch #14 working for me with latest Panopoly + Radix. Thanks @dsnopek.
Comment #18
dsnopek@arshadcn: So, what you're saying is "reviewed & tested by the community"? :-)
Comment #19
hass commented@jessebearch: Are you able to commit this patch, please? What is holding it back?
Comment #20
jessebeach commentedhass, I've just yesterday backported all of the D8 Toolbar prefixing we did back to the Navbar. This issue should be addressed through that work in the latest 7.x-1.x dev branch.
Comment #21
hass commentedSeems not fixed. Found classes
In rtl css files class names like:
And tons of others.
And many
[dir="rtl"]in LTR filesAnd found an id named
toolbar-itemwhat is D8Comment #22
jessebeach commentedThanks for the honesty-check :) Forgot that D7 doesn't have [dir="rtl"] by default. On it.
Comment #23
jessebeach commentedWhere did you find col-4 and col-2?
Comment #24
jessebeach commentedOh, in navbar.tpl.php. I don't think that's even being used!
Comment #25
jessebeach commentedRemoved an unused template file. (86fc9147224843dba0429d490532cca9503ebf15)
Comment #26
jessebeach commentedhass, can you review the 7.x-1.x branch and make sure I got everything?
Comment #27
hass commentedThanks for quick fixes. I try my best, but it may need to wait until next weekend.
Comment #28
hass commentedFound this bug #2119989: Add navbar_menu_tree() to prevent theme clashes
Comment #29
hass commentedLooks good for now, but please see all the CNR cases I attached patches, too.
Comment #30
hass commentedNope, there are still 44 matches for
[dir="rtl"]that are not located in rtl CSS files.Comment #31
jessebeach commentedAll the
[dir="rtl"]references are deleted and the RTL files are updated. I think everything should be good now.Which patches specifically, hass? I'll have a look through.
Comment #32
koppie commentedThere's no new patch so I guess you simply rolled the changes into the latest dev? I also discovered the hard way that if you upgrade navbar to dev, you also have to upgrade breakpoints (see #1938162: Drupal Update Is Unreliably HORRIBLE).
In any case I still don't see any improvement in navbar with the Bootstrap theme.
Comment #33
hass commentedCheck out if the .menu class is the root cause of all your issues. It's the only remaining critical issue, but that is a different case
Comment #34
jessebeach commented@koppie, can you provide a screenshot of the issues? I'll load the theme as well, but having a screenshot will help me understand the specific issues you are running into.
Comment #35
jessebeach commentedI loaded up Bootstrap 3. The only major issue I noticed is the width of the menu tray is too narrow. I made a commit to change the width unit from rem to em to solve this.
0a52368206c1609cb882a0adab37a8ee8851af9d
Otherwise, everything looks to be styled within an acceptable range, no?
Please ignore the arrow in the image below. It's not meant to point at anything. The process of uploading and referencing an image is to cumbersome for me to run through it again :/
Comment #36
jessebeach commentedComment #37
jessebeach commentedComment #38
jessebeach commentedComment #39
koppie commentedI'm seeing the same problem as @busa in #11; screenshot attached.
Comment #40
koppie commentedComment #41
jessebeach commented@koppie and @busa, the Bootstrap theme overrides
theme_item_listand removes the<div class="item-list"></div>wrapper around theul.theme_item_listis a system theme function. It's kind of like an API for front end code. If you change this API, you're going to get unexpected behavior. So in this case, I consider this a bug with Bootstrap, not Responsive Preview which is depending on Drupal system-level theme functions.Check out
/theme/system/item-list.func.phpin bootstrap and log an issue about this in the theme. If you get this div back into the theme function, Responsive Preview will work, otherwise you'll have to skip this module or override Bootstrap's override oftheme_item_listto make it match the system output again.Comment #42
jessebeach commentedComment #43
jessebeach commentedI found two issues with Bootstrap that are overrideable with CSS.
I've committed them as: 2ee91d225409edfac7e785c1f812974640637275 and 5590dc8c9279e040244799360485d23a4d6cdf87. The code is:
This theme really needs to be less global about its resets :/
And
Comment #44
jessebeach commentedI'm going to set this issue to fixed. If we find specific problems from here on out, we can log them separately.