On 12/01/16 11:22, Matthias Runge wrote:
>
> https://launchpad.net/bugs/1532759
>
> Unfortunately, that even hasn't been detected by tests.
>
https://github.com/openstack/horizon/commit/871505c130cf1fd02aae41aeb8f6062af4a5fe88
fixes this issue (another revert).
Matthias
> El 12 ene 2016, a las 11:22, Matthias Runge escribió:
>
> On 12/01/16 03:33, Richard Jones wrote:
>> The tag addition has had to be reverted as it broke other parts
>> of the application (notably lazy loaded tabs like Instance Details), sadly.
>>
>> Regarding which router to use - I've used
On 12/01/16 03:33, Richard Jones wrote:
> The tag addition has had to be reverted as it broke other parts
> of the application (notably lazy loaded tabs like Instance Details), sadly.
>
> Regarding which router to use - I've used the built-in router in the
> past quite successfully. I think I'd w
The tag addition has had to be reverted as it broke other parts of
the application (notably lazy loaded tabs like Instance Details), sadly.
Regarding which router to use - I've used the built-in router in the past
quite successfully. I think I'd want to see a solid reason for using a 3rd
party on
Rajat,
Thanks for starting some discussion here. I think your target=“_self” is taken
care of now, right?
Re: ng-route vs ui-router - everything I have ever seen or been told supports
using ui-router instead of ng-route. I know a quick google search supports
that, but let me google that for
