Closed cedx closed 8 years ago
Hi Cédric,
I changed the code and published library on Pub. Please use latest version (0.6.10) to check is my changes fix issue you mentioned here.
The output has changed but it is still here :
Transition cancelled
STACKTRACE:
null
The carousel is still working fine.
I made other changes regarding to your logs. Please use latest version (0.6.11) to check is changes help. If it doesn't help - I need info to repeat this issue.
Same output and behavior as before (e.g. Transition cancelled
printed and no stack trace). But I think the issue is fixed when I look (naively) at your code.
The unique statement that I don't understand is on line 133:
_currentTransition.completeError('Transition cancelled');
Why do you consider that the transition cancellation should complete as an error? In the current case, this is exactly what occurs: a transition is in progress, but a route change interrupts it. This is a standard behavior of stopping the transition as we are changing the page content, thus removing the carousel.
In what other cases transition cancellation occurs?
I close this issue as the bug is fixed for me :) The console output is not anymore related to the raised bug.
Ok.
I don't know if it's really an issue as this is not blocking, and I'm quite novice in AngularDart development.
I've a carousel on several pages of my application. Their slides are a populated by a REST service when the page components are instantiated by Angular. The navigation between the pages is handled with the standard routing and
ng-view
components.Everything is working fine. No problem from the point of view of an end user. But sometimes, when I navigate from a page containing a carousel to another page, the following output is printed in my Dev Tools console:
This happens with Dartium, as well as with compiled JS under Chrome.
Dart: 1.12.1 AngularDart: 1.1.2 AngularUI: 0.6.9 WebComponents: 0.12.0