You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I have really small requests (a few ms only), the spinner works .. but for larger requests (where the icon needs to spin for a longer period of time) it 'crashes' .. as in the button remains disabled, but the spinner is static instead of continuously spinning
This happens on ionic 3 and angular 5
I can post a video if the above comment doesn't make any sense
I am just using: <button ion-button color="orange" round (click)="goToReadBook(book)" [ladda]="loadingService.isActive">Citeste</button>
And the isActive is made active before the request, and isActive is made false when the request is over, in either .then or .catch
Do you guys know what could be wrong ?
The text was updated successfully, but these errors were encountered:
I don't have experience with Ionic, so I'm not sure if that might be causing an issue. However, there are a bunch of things you can try to narrow down the problem:
Is the issue reproducible in other browsers?
Exactly how long does the progress indicator spin before it freezes?
Does the problem still occur if the Ionic attributes are removed from the button?
Does updating to the latest version of Angular and Ionic fix the issue?
When I have really small requests (a few ms only), the spinner works .. but for larger requests (where the icon needs to spin for a longer period of time) it 'crashes' .. as in the button remains disabled, but the spinner is static instead of continuously spinning
This happens on ionic 3 and angular 5
I can post a video if the above comment doesn't make any sense
I am just using:
<button ion-button color="orange" round (click)="goToReadBook(book)" [ladda]="loadingService.isActive">Citeste</button>
And the isActive is made active before the request, and isActive is made false when the request is over, in either .then or .catch
Do you guys know what could be wrong ?
The text was updated successfully, but these errors were encountered: