Crystal Taggart
Posts: 0
Joined: Tue Aug 26, 2014 3:16 am

BETA Bootstrap/Angular JS feedback: When using a link within a navbar, the link isn't populating the URL.

BETA Bootstrap/Angular JS feedback: For some reason when using the link within a navbar, the link isn't populating the URL.

Steps to reproduce:

  1. Add a navbar control.

  2. Add a link into the navbar

  3. Set the URL (not working - link shows javascript:void(0))

  4. Tried adding the ng-click event to call a method (also not working) - the HTML generated looks like this http://screencast.com/t/NsvM1SR8Vik6

    Regular links outside the navbar work fine although it took a bit to figure out the URL scheme.

Crystal Taggart
Posts: 0
Joined: Tue Aug 26, 2014 3:16 am

BETA Bootstrap/Angular JS feedback: When using a link within a navbar, the link isn't populating the URL.

Just one clarification, both the navbar and the navs aren't working.

Egor Kotov6832188
Posts: 0
Joined: Wed Nov 19, 2014 5:15 pm

BETA Bootstrap/Angular JS feedback: When using a link within a navbar, the link isn't populating the URL.

Hello Crystal,
just for clarification it wasn't working when you pressed on it ?

Illya Stepanov
Posts: 0
Joined: Mon Mar 18, 2013 8:48 am

BETA Bootstrap/Angular JS feedback: When using a link within a navbar, the link isn't populating the URL.

Hi Crystal --

Thank you for your feedback.
Yes, it's a bug we will report it.

Illya Stepanov
Posts: 0
Joined: Mon Mar 18, 2013 8:48 am

BETA Bootstrap/Angular JS feedback: When using a link within a navbar, the link isn't populating the URL.

Crystal --

For now as long we're fixing this bug you can use this workaround:

  1. In Scope define function for example 'linkURL' and add code:
    precodevar $window = Apperyio.get("$window");
    $window.location.href = "http://google.com&quot/code/pre

  2. In your Link component in NavBar menu - define attribute 'ng-click' with function name as defined in scope e.g. "linkURL()".

    Note: this could be not work in Chrome with mobile-frame (you can test without it), but should work correctly in Safari.

Return to “Issues”