Responsive navbar #738

ravipunjwani · 2016-09-15T03:00:45Z

Hi guys,
This library is just an awesome box to start with angular while dependent on bootstrap css. I'm creating a navbar and just got through an issue here. Probably it's a new-feature request or it can be said as a bootstrap-feature not yet in ng-bootstrap.

Feature description:

Look at this link where you can set collapsible navbar based on the size of the screen.
Bootstrap 4 documentation for navbar

This can be seen in responsive navbar section of this link. To the point, it actually uses navbar-toggleable-xs class to define this functionality. The navbar comes collapsible only when the screen size is xs, otherwise, its a regular navbar.

Version of Angular, ng-bootstrap, and Bootstrap:

Angular2: 2.0.1

ng-bootstrap: 1.0.0-alpha.6

Bootstrap: 4.0.0-alpha.4

The text was updated successfully, but these errors were encountered:

jnizet · 2016-09-15T06:10:57Z

Hi @ravipunjwani

We already have the NgbCollapse directive to do that. Replace the bootstrap example by the following snippet, and you'll have the equivalent.

Is there something more needed?

<nav class="navbar navbar-light bg-faded">
  <button class="navbar-toggler hidden-sm-up" type="button" (click)="isNavbarCollapsed = !isNavbarCollapsed" aria-controls="exCollapsingNavbar2" aria-expanded="false" aria-label="Toggle navigation">
    &#9776;
  </button>
  <div [ngbCollapse]="isNavbarCollapsed" class="collapse navbar-toggleable-xs" id="exCollapsingNavbar2">
    <a class="navbar-brand" href="#">Responsive navbar</a>
    <ul class="nav navbar-nav">
      <li class="nav-item active">
        <a class="nav-link" href="#">Home <span class="sr-only">(current)</span></a>
      </li>
      <li class="nav-item">
        <a class="nav-link" href="#">Features</a>
      </li>
      <li class="nav-item">
        <a class="nav-link" href="#">Pricing</a>
      </li>
      <li class="nav-item">
        <a class="nav-link" href="#">About</a>
      </li>
    </ul>
  </div>
</nav>

pkozlowski-opensource · 2016-09-15T08:57:04Z

Yep, agree with @jnizet - I think that we are covered here so going to close this one. @ravipunjwani feel free to come back with more info if you believe that we are still missing sth.

ravipunjwani · 2016-10-02T23:57:56Z

Hi @jnizet and @pkozlowski-opensource ,

I'm coming back on this issue after many days as I got busy with building rest of my app. Kindly have a look at my explanation below for this issue.

I agree that the ng-collapse is already a feature in ng-bootstrap library but, it works only on a variable e.g. isNavbarCollapsed. That means the variable can be initialized to a value true or false, but this behaviour remains same with all screen sizes.

I would think of a "responsive navbar" that works same as in current example that you provided, additionally with a little logic as follows:

in small screen sizes, it should open collapsed. It would look weird when you open an app on mobile and the first think you see is the "expanded navigation".
in large screen, it should not be collapsed by default.

Please refer to the sample plunker to describe the problem with code and a little explanation.
http://plnkr.co/edit/0T9TK36RHzZGW9dIBvJf?p=preview

The bootstrap implementation works well as I described. Please follow the second example in bootstrap responsive navbar.

The key here is the usage of class "navbar-toggleable-xs".

ravipunjwani · 2016-10-05T01:24:27Z

Hi @pkozlowski-opensource, please update the task status to Open, so that anyone can look into this issue and suggest the feature change.

pkozlowski-opensource · 2016-10-17T19:25:06Z

@ravipunjwani I had another look at this one and IMO we do behave exactly as BS.

Here is a simple plunker I've created: http://plnkr.co/edit/4GJl2bBLsjHGhEjn48hx?p=preview
As far as I can tell it matches 1:1 behaviour of the demo http://v4-alpha.getbootstrap.com/components/navbar/#collapsible-content

The way the display of the navbar is driven is be CSS only and there is no JS logic in collapse nor in any other place (at least as far as I can tell).

If you are after setting the initial state of the collapse you could do it based on the viewport size or use sth fancy like media queries from JS: https://www.sitepoint.com/javascript-media-queries/. In any case I don't think there should be any logic for this on the ng-bootstrap side.

Given all the above I'm going to close this issue for now. Open to re-considering if you can demonstrate that we are behaving differently as compared to Bootstrap 4.

rolandoldengarm · 2016-10-19T07:41:58Z

While I agree that with collapse you can implement the navbar, it would be even better to implement a navbar component that USES Collapse..
That way there's a one-on-one mapping from bs4 components to ng-bootstrap components.

This is the same approach we've taken for ng-officeuifabric, and you end up with some very simple components, but for the end user it's very easy and there's no discussion about which directive/component to use.
My main concern with your approach here is that the user needs to copy/paste HTML and worry about other stuff like responsiveness, while I think that should be handled by ng-bootstrap. @pkozlowski-opensource

pkozlowski-opensource · 2016-10-19T08:00:15Z

While I agree that with collapse you can implement the navbar, it would be even better to implement a navbar component that USES Collapse..

The problem with a dedicated navbar component is that you would have to take arbitrary decisions that might limit what users can do (less flexibility). Indeed a component would have to have a template and any markup you put in this template harder to customize by users.

Having said the above I'm not opposed to the idea of a navbar component, I'm just trying to determine if the gain (less code to write etc.) vs. flexibility makes it "worth". Basically if the new abstraction "pays for itself" (any new abstraction has cost on a new API, documentation, things to learn etc.)

@rolandoldengarm if you (or anyone else interested in this feature) could put together a design doc / API proposal we could iterate on it and see if its is worth new API.

Supratentorial · 2017-01-07T03:50:43Z

@pkozlowski-opensource Plunker is not working. Locally I get the same result as the Plunker.

datumgeek · 2017-01-16T10:49:09Z

i had the above example working, but then upgraded to bootstrap@4.0.0-alpha.6 (from bootstrap@4.0.0-alpha5) and it stopped working.

i noticed that there is a navbar rewrite

i changed my menu like this (and it works now) 😄

<nav class="navbar navbar-toggleable-md navbar-light bg-faded">
  <button class="navbar-toggler navbar-toggler-right" type="button" (click)="isNavbarCollapsed = !isNavbarCollapsed"
          aria-controls="exCollapsingNavbar2" aria-expanded="false" aria-label="Toggle navigation">
    <span class="navbar-toggler-icon"></span>
  </button>
  <a class="navbar-brand" href="#">North America - Conventional</a>
  <div [ngbCollapse]="isNavbarCollapsed" class="collapse navbar-collapse" id="exCollapsingNavbar2">
    <div class="navbar-nav mr-auto">
      <a class="nav-item nav-link" routerLink="/transfers" routerLinkActive="active">Transfers</a>
      <a class="nav-item nav-link" routerLink="/jobs" routerLinkActive="active">Jobs</a>
      <a class="nav-item nav-link" routerLink="/jobs/7" routerLinkActive="active">Job 7</a>
    </div>
  </div>
</nav>

xmlking · 2017-02-11T21:23:44Z

we need auto collapse for ngbCollapse when any link under it clicked:
jquery e.g:

    $('.navbar-collapse ul li a').click(function() {
        /* always close responsive nav after click */
        $('.navbar-toggle:visible').click();
    });

JohnGalt1717 · 2017-03-13T13:29:46Z

Even with @datumgeek 's fixes this still doesn't work properly because it doesn't know about reactive design and automatically set it correctly as those change.

There needs to be an out of the box navbar that works EXACTLY like the bootstrap example that understands reactive design and works accordingly.

That means:

When it MD or Large the full menu is visible with no button.
When xs or sm the menu is automatically hidden and the button shows up and they can tap on the menu to show it.
If you drag your window size it should automatically react to the size change and when large enough the button should go away and the menu should automatically display and when small enough going back the other way the menu should hide and the button should show.

What it doesn't do right now is know the different sizing and change the value based on reactive design.

I.e. you need a proper navbar control in here because this hack you have right now doesn't actually address the issue and you're requiring major code just to make work what works right out of the box with bootstrap 4 which defeats the purpose of this project.

clarkj · 2017-04-21T00:30:23Z

Has anyone had any success adding a dropdown-link to a navbar? @datumgeek 's solution works for me, but using ngbCollapse with a dropdown inside the navbar results in the dropdown getting put inside the navbar element, not on the body.

This is what I tried:

<nav class="navbar navbar-toggleable-xl navbar-light bg-faded">
        <a class="navbar-brand" routerLink="/">Ember</a>
	 <div class="collapse navbar-collapse">
		<div class="navbar-nav">
			<a class="nav-item nav-link" routerLink="/table" routerLinkActive="active">AR Table</a>
			<a class="nav-item nav-link" routerLink="/analytics" routerLinkActive="active">Dashboard</a>
			<a class="nav-item nav-link disabled"> Workbench</a>
		</div>
		<ul class="nav navbar-nav">
			<li class="nav-item dropdown dropdown-append-to-body">
				<a class="nav-link dropdown-toggle" (click)="navbar.dropdown=!navbar.dropdown" routerLink="/table" id="navbarDropdownMenuLink" [attr.aria-expanded]="dropdown" aria-controlls="collapseExample">Dropdown link</a>
			        <div id = "collapseExample" [ngbCollapse]="!navbar.dropdown" class="dropdown-menu">
					<a class="dropdown-item" href="#">Action</a>
					<a class="dropdown-item" href="#">Another action</a>
					<a class="dropdown-item" href="#">Something else here</a>
				</div>
			</li>
		</ul>
	</div>
	<div class="ml-auto">
		<div class="navbar-nav">
			<a class="nav-item user">test</a>
		</div>
	</div>
</nav>

wuttke · 2017-06-19T15:30:40Z

Works for me (except for initial state which is not collapsed but should be).

Here is how I did the dropDown:

      <li class="nav-item dropdown">
        <div ngbDropdown>
          <a ngbDropdownToggle class="nav-link dropdown-toggle" id="dropdown_mod">TITLE</a>
          <div class="dropdown-menu" aria-labelledby="dropdown_mod">
            <a class="dropdown-item" href="#" *ngFor="let area of areas">{{area}}</a>
          </div>
        </div>
      </li>

dougamos · 2017-07-31T10:47:35Z

I was able to replicate bootstraps navbar example with the collapse directive except for animation. The collapse plugin doesn't seem to do the slide in/out animation.

collindutter · 2017-08-07T21:46:37Z

Are there plans to implement the slide in/out animation?

AnthonyCrowcroft · 2017-08-14T02:27:44Z

I'm finding that neither of these code snippets are working with the current versions of bootstrap and ng-bootstrap. Is there still no plans to implement this and if there isn't is there any chance that there could be a plunker kept up to date.

mcescalante · 2017-08-14T19:30:31Z

I find the same thing as @AnthonyCrowcroft - the snippets used to work but with the 4.0.0-beta updates, it seems to have changed some syntax and stuff. Yes, I can figure it out myself. I don't want a dedicated page in the docs for this since I agree that [ngbCollapse] can handle it, but it would be really helpful to have a plunkr or even just updated gist with the latest working navbar collapse code. If I end up with some working code this afternoon I will update this comment with a gist of my own.

pkozlowski-opensource · 2017-08-14T19:42:23Z

@mcescalante you can always check our demo page code where we've got responsive navbar:

ng-bootstrap/demo/src/app/app.component.html

Lines 2 to 41 in 5886946

    
           <header class="navbar navbar-light navbar-fixed-top navbar-expand-lg"> 
        
             <a class="navbar-brand" [routerLink]="['/']" (click)="navbarCollapsed = true">ng-bootstrap</a> 
        
             <button class="navbar-toggler navbar-toggler-right" type="button" (click)="navbarCollapsed = !navbarCollapsed" 
        
                     [attr.aria-expanded]="!navbarCollapsed" aria-controls="navbarContent" aria-expanded="false" aria-label="Toggle navigation"> 
        
               <span class="navbar-toggler-icon"></span> 
        
             </button> 
        
             <div class="navbar-collapse" [ngbCollapse]="navbarCollapsed" id="navbarContent"> 
        
               <ul class="navbar-nav mr-auto"> 
        
                 <li class="nav-item" [routerLinkActive]="['active']"> 
        
                   <a class="nav-link" [routerLink]="['/getting-started']" (click)="navbarCollapsed = true">Getting Started</a> 
        
                 </li> 
        
                 <li class="nav-item" [routerLinkActive]="['active']"> 
        
                   <a class="nav-link" [routerLink]="['/components']" (click)="navbarCollapsed = true">Components</a> 
        
                 </li> 
        
                 <li class="nav-item d-lg-none" *ngFor="let component of components" [routerLinkActive]="['active']"> 
        
                   <a class="nav-link" [routerLink]="['/components', component.toLowerCase()]" (click)="navbarCollapsed = true">{{ component }}</a> 
        
                 </li> 
        
               </ul> 
        
               <span class="github-buttons d-none d-lg-inline"> 
        
                 <a class="github-button" 
        
                    href="https://github.com/ng-bootstrap/ng-bootstrap" 
        
                    target="_blank" 
        
                    data-style="mega" 
        
                    data-count-href="/ng-bootstrap/ng-bootstrap/stargazers" 
        
                    data-count-api="/repos/ng-bootstrap/ng-bootstrap#stargazers_count" 
        
                    data-count-aria-label="# stargazers on GitHub" 
        
                    aria-label="Star ng-bootstrap/ng-bootstrap on GitHub">Star</a> 
        
                 <a href="https://twitter.com/intent/tweet?button_hashtag=ngbootstrap" 
        
                    class="twitter-hashtag-button" 
        
                    data-size="large" 
        
                    data-text="I&#39;m checking out ng-bootstrap, THE Angular UI framework for Bootstrap CSS" 
        
                    data-url="https://ng-bootstrap.github.io" 
        
                    data-show-count="true">Tweet #ngbootstrap</a> 
        
               </span> 
        
             </div> 
        
           </header>

mcescalante · 2017-08-14T20:39:50Z

Ah excellent! This is perfect @pkozlowski-opensource thank you very much!

kerryhatcher · 2017-08-29T14:39:31Z

@pkozlowski-opensource That snippet was exactly what I was looking for. Methinks there needs to be something in the docs about this. Wasn't obvious to me as a newbie ng-bootstrap user (but long time bootstrap user)

chedched · 2017-09-17T17:11:49Z

Does anyone have a plunkr for the latest version? I don't manage to make it run.

kamok · 2017-10-13T20:22:41Z

I wanted to try Bootstrap 4 in hopes of getting access to some of their new goodies, but seeing how it's so difficult to get something as simple as a navbar to work is quite disheartening. The code on the documentation for Bootstrap 4 simply doesn't work with the latest version of Angular. The code from @pkozlowski-opensource works, but it seems like a lot of hoops and hurdles just to get one of the most basic components to work. (The hurdle being having to look up issues in ng-bootstrap when it should just work)

brijmcq · 2017-10-19T07:20:57Z

@dougamos @collindutter You can add the angular/animations to have that slide-in/out effect.

<nav class="navbar navbar-expand-lg navbar-dark bg-dark fixed-top">
	<div class="container">
		<a href="#" class="navbar-brand">ngbs-1</a>
     <button class="navbar-toggler" (click)="toggleNavbar()"  type="button" aria-controls="theNavbar" aria-expanded="false" aria-label="Toggle navigation">
    <span class="navbar-toggler-icon"></span>
  </button>
		<div [ngbCollapse]="isNavbarCollapsed" id="theNavbar"
     [@collapse]="isNavbarCollapsedAnim"
     class="navbar-collapse collapse navbar-toggleable">
			<ul class="navbar-nav mr-auto ml-auto"> 
				<li class="nav-item">
					<a class="nav-link" href="#"> Home</a>
				</li>
				<li class="nav-item">
					<a class="nav-link" href="#"> About</a>
				</li>
				<li class="nav-item">
					<a class="nav-link" href="#"> Contact</a>
				</li>
			</ul>
		</div>
	</div>
</nav>

And in your component

import {  trigger,state,style, animate, transition } from '@angular/animations'; 
@Component({
  selector: 'my-app',
  templateUrl: './app.component.html',
  styleUrls: ['./app.component.scss'],
   animations: [
  trigger('collapse', [
    state('open', style({
      opacity: '1'
    })),
    state('closed',   style({
      opacity: '0',
      display: 'none',   
    })),
    transition('closed => open', animate('400ms ease-in')),
    transition('open => closed', animate('100ms ease-out'))
  ])
]
})
export class AppComponent {
  isNavbarCollapsed = true;
  _isNavbarCollapsedAnim = 'closed';
  ngOnInit() {
    this.onResize(window);
  }
  @HostListener('window:resize', ['$event.target']) 
onResize(event) { 
  if(event.innerWidth > 990){
    //need to set this to 'open' for large screens to show up because of opacity in 'closed' animation.
    this._isNavbarCollapsedAnim = 'open';
      this.isNavbarCollapsed = true;
  }else{
    // comment this line if you don't want to collapse the navbar when window is resized.
   // this._isNavbarCollapsedAnim = 'closed';
  }
}
  toggleNavbar(): void {
    if(this.isNavbarCollapsed){
        this._isNavbarCollapsedAnim = 'open';
      this.isNavbarCollapsed = false;
    } else {
    this._isNavbarCollapsedAnim = 'closed';
      this.isNavbarCollapsed = true;
    }
  }
  get isNavbarCollapsedAnim() : string {
    return this._isNavbarCollapsedAnim;
  }
}

Here's a stackblitz demo https://stackblitz.com/edit/ng-bri-bs1-armbhz?file=app%2Fapp.component.html

- Upgraded to bootstrap v4 beta2 - Removed bootstrap JS - Added ng-bootstrap - Fixed menu (now works with mobile devices) as per example of ng-bootstrap/ng-bootstrap#738 (comment)

yanshuf0 · 2018-02-25T08:05:34Z

Lol this is actually bs that the accepted answer was "here's this directive which doesn't do 90% of what the bootstrap component does, but deal with it." Paste the code from the first response into your ide and compare it with the BS4 component. Just terrible. I also like how the last response is 50+ lines of code to do what the BS4 component does in one. Defeating the purpose of using bootstrap, or angular for that matter. Why not just use es5 and some html and css, technically you COULD achieve everything bootstrap offers. Sad!

Louspirit · 2018-06-28T15:57:27Z

I found this interesting article that explains the purpose of ng-bootstrap and why we shouldn't give it up (even if we have to write more code) : https://stevenschwenke.de/AngularAndBootstrapUseNg-bootstrap.

Basically Angular works with components where jquery interacts with the DOM itself. While Jquery can break the app, ng-bootstrap is written the angular way and you keep the control over your components.

matthiasbraun · 2018-07-11T15:41:16Z

The default ngbCollapse example works also for small initial screen sizes, if you set the initial value of isCollapsed to true (even if this is not really "true" for larger screen sizes, but it works)

samantha-holder · 2018-09-20T18:50:04Z

The ngbCollapse is only tied to the onclick button action though. If you increase the window size to hide the 'hamburger' button the 'show' property is still active on the div. Then next time you reduce window size you'll see an already active dropdown. The collapsed menu should be hidden by default every time the 'hamburger' makes an appearance. It should not persisted.

benjavalero · 2019-07-25T09:17:40Z

For me, just adding (click)="navbarCollapsed = true" to the a links has made the trick:

@mcescalante you can always check our demo page code where we've got responsive navbar:

ng-bootstrap/demo/src/app/app.component.html

Lines 2 to 41 in 5886946

<header class="navbar navbar-light navbar-fixed-top navbar-expand-lg">

<a class="navbar-brand" [routerLink]="['/']" (click)="navbarCollapsed = true">ng-bootstrap</a>

<button class="navbar-toggler navbar-toggler-right" type="button" (click)="navbarCollapsed = !navbarCollapsed"

[attr.aria-expanded]="!navbarCollapsed" aria-controls="navbarContent" aria-expanded="false" aria-label="Toggle navigation">

<span class="navbar-toggler-icon"></span>

</button>

<div class="navbar-collapse" [ngbCollapse]="navbarCollapsed" id="navbarContent">

<ul class="navbar-nav mr-auto">

<li class="nav-item" [routerLinkActive]="['active']">

<a class="nav-link" [routerLink]="['/getting-started']" (click)="navbarCollapsed = true">Getting Started</a>

</li>

<li class="nav-item" [routerLinkActive]="['active']">

<a class="nav-link" [routerLink]="['/components']" (click)="navbarCollapsed = true">Components</a>

</li>

<li class="nav-item d-lg-none" *ngFor="let component of components" [routerLinkActive]="['active']">

<a class="nav-link" [routerLink]="['/components', component.toLowerCase()]" (click)="navbarCollapsed = true">{{ component }}</a>

</li>

</ul>

<span class="github-buttons d-none d-lg-inline">

<a class="github-button"

href="https://github.com/ng-bootstrap/ng-bootstrap"

target="_blank"

data-style="mega"

data-count-href="/ng-bootstrap/ng-bootstrap/stargazers"

data-count-api="/repos/ng-bootstrap/ng-bootstrap#stargazers_count"

data-count-aria-label="# stargazers on GitHub"

aria-label="Star ng-bootstrap/ng-bootstrap on GitHub">Star</a>

<a href="https://twitter.com/intent/tweet?button_hashtag=ngbootstrap"

class="twitter-hashtag-button"

data-size="large"

data-text="I'm checking out ng-bootstrap, THE Angular UI framework for Bootstrap CSS"

data-url="https://ng-bootstrap.github.io"

data-show-count="true">Tweet #ngbootstrap</a>

</span>

</div>

</header>

moolsbytheway · 2021-03-14T21:01:45Z

FYI: These two examples works just fine
https://embed.plnkr.co/plunk/xH6VJo
https://stackblitz.com/run?file=src%2Fapp%2Fcollapse-navbar.html

AtozEvo · 2021-11-11T05:35:43Z

I would just like to raise an opinion as a new @ng-bootstrap/ng-bootstrap / boostrap use (with angular). I think there should at least be a Navbar 'page' on the docs to explain that Navbar is basically implementing ngbCollaspe.

After a bunch of searching (and googling, and thinking "There's no way ng-boostrap wouldn't have a navbar component since bootstrap has one") I stumbled on the doc/example in nbgCollaspe's document. My first thought was, "Why is it here?".

Maybe move the Responsive Navbar section in the ngbCollaspe page to its own page or have a link 'components/collapse/examples#navbar' on a navbar page. I mean, the fragment is already called 'navbar'. I'm just thinking it'll be easier to find for newbies.

pkozlowski-opensource closed this as completed Sep 15, 2016

ghost mentioned this issue Sep 23, 2016

feat(navbar): Support for bootstrap navbar valor-software/ngx-bootstrap#540

Open

pkozlowski-opensource reopened this Oct 5, 2016

pkozlowski-opensource added needs: investigation type: feature labels Oct 5, 2016

pkozlowski-opensource closed this as completed Oct 17, 2016

pkozlowski-opensource mentioned this issue Oct 19, 2016

Feature request: Navbar #907

Closed

briantopping mentioned this issue Nov 1, 2016

1:1 Mapping to Bootstrap Components #993

Closed

pkozlowski-opensource mentioned this issue Jan 26, 2017

Feature: Navigation Bar #1260

Closed

pkozlowski-opensource mentioned this issue Jul 9, 2017

Any plan to add support for navbars (and responsive behaviour)? #1664

Closed

This was referenced Dec 13, 2018

Docs: navbar #2928

Closed

hamburger menu not working #2919

Closed

johnruck mentioned this issue Jul 19, 2019

Demo isnt working on https://ng-bootstrap.github.io/ anymore #3304

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Responsive navbar #738

Responsive navbar #738

ravipunjwani commented Sep 15, 2016 •

edited

jnizet commented Sep 15, 2016

pkozlowski-opensource commented Sep 15, 2016

ravipunjwani commented Oct 2, 2016

ravipunjwani commented Oct 5, 2016

pkozlowski-opensource commented Oct 17, 2016

rolandoldengarm commented Oct 19, 2016

pkozlowski-opensource commented Oct 19, 2016

Supratentorial commented Jan 7, 2017

datumgeek commented Jan 16, 2017

xmlking commented Feb 11, 2017 •

edited

JohnGalt1717 commented Mar 13, 2017

clarkj commented Apr 21, 2017

wuttke commented Jun 19, 2017

dougamos commented Jul 31, 2017

collindutter commented Aug 7, 2017

AnthonyCrowcroft commented Aug 14, 2017

mcescalante commented Aug 14, 2017 •

edited

pkozlowski-opensource commented Aug 14, 2017

mcescalante commented Aug 14, 2017

kerryhatcher commented Aug 29, 2017

chedched commented Sep 17, 2017

kamok commented Oct 13, 2017 •

edited

brijmcq commented Oct 19, 2017 •

edited

yanshuf0 commented Feb 25, 2018 •

edited

Louspirit commented Jun 28, 2018 •

edited

matthiasbraun commented Jul 11, 2018

samantha-holder commented Sep 20, 2018

benjavalero commented Jul 25, 2019

moolsbytheway commented Mar 14, 2021 •

edited

AtozEvo commented Nov 11, 2021

Responsive navbar #738

Responsive navbar #738

Comments

ravipunjwani commented Sep 15, 2016 • edited

Feature description:

Version of Angular, ng-bootstrap, and Bootstrap:

jnizet commented Sep 15, 2016

pkozlowski-opensource commented Sep 15, 2016

ravipunjwani commented Oct 2, 2016

ravipunjwani commented Oct 5, 2016

pkozlowski-opensource commented Oct 17, 2016

rolandoldengarm commented Oct 19, 2016

pkozlowski-opensource commented Oct 19, 2016

Supratentorial commented Jan 7, 2017

datumgeek commented Jan 16, 2017

xmlking commented Feb 11, 2017 • edited

JohnGalt1717 commented Mar 13, 2017

clarkj commented Apr 21, 2017

wuttke commented Jun 19, 2017

dougamos commented Jul 31, 2017

collindutter commented Aug 7, 2017

AnthonyCrowcroft commented Aug 14, 2017

mcescalante commented Aug 14, 2017 • edited

pkozlowski-opensource commented Aug 14, 2017

mcescalante commented Aug 14, 2017

kerryhatcher commented Aug 29, 2017

chedched commented Sep 17, 2017

kamok commented Oct 13, 2017 • edited

brijmcq commented Oct 19, 2017 • edited

yanshuf0 commented Feb 25, 2018 • edited

Louspirit commented Jun 28, 2018 • edited

matthiasbraun commented Jul 11, 2018

samantha-holder commented Sep 20, 2018

benjavalero commented Jul 25, 2019

moolsbytheway commented Mar 14, 2021 • edited

AtozEvo commented Nov 11, 2021

ravipunjwani commented Sep 15, 2016 •

edited

xmlking commented Feb 11, 2017 •

edited

mcescalante commented Aug 14, 2017 •

edited

kamok commented Oct 13, 2017 •

edited

brijmcq commented Oct 19, 2017 •

edited

yanshuf0 commented Feb 25, 2018 •

edited

Louspirit commented Jun 28, 2018 •

edited

moolsbytheway commented Mar 14, 2021 •

edited