> El 12 ene 2016, a las 11:22, Matthias Runge <mru...@redhat.com> escribió:
> 
> On 12/01/16 03:33, Richard Jones wrote:
>> The <base> 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 one. It could be that nested routes are part of that,
>> but I kinda see that as a convenience thing, unless I'm missing
>> something core to how routing is planned to be done. Then again we
>> really haven't had any discussion about how we see routing work. The one
>> patch that's up that uses routing seems perfectly able to do so without
>> needing extended capabilities of 3rd party routers.
> 
> I believe, there has been something else messing up with routing,
> causing pagination to be broken now.
> 
> https://launchpad.net/bugs/1532759
> 
> Unfortunately, that even hasn't been detected by tests.
> 
> Matthias
> 
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Also see https://bugs.launchpad.net/horizon/+bug/1532265

Any link that has an href="#" is probably broken.

If I'm not mistaken, the # is what angular uses as locationprovider?

Itxaka
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to