-
Notifications
You must be signed in to change notification settings - Fork 256
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
angular-busy not fading the backdrop for some of the input fields in html page while promise is running #33
Comments
Can you create a plnkr or similar that demonstrates the issue. |
Here is the plunkr link... You can type anything in those two text boxes. You will see as the promise chain is running everything fades away except the url text box. Here I have use alert box to end the chain. I researched a bit more and found that the 'input-group' class that I am using to add an 'https://' input-group-addon to the text box for formatting provided by bootstrap is not allowing that particular text box to fade. When I removed that input-group class, it worked fine.
Wondering how can I make this angular-busy work with this particular bootstrap class |
It looks like there's a z-index issue. For now, add a style like this to your app: .cg-busy { I'll fix this in a later release. |
Thanks for responding to my message and helping me out. Sure will add this to my css and will wait for your update :) |
Thanks @MeghaY and @cgross, I iterated on ur previous plnkr and yes the workaround is nice! |
Fixed in v4.1 |
Hello,
Using cg-busy directive in div tag, it should fade/blured that whole div tag's content while the promise is running behind the scenes right. I have cg-busy running all fine in other pages in my angularjs project. But with one of the html page design, one of the input field doesn't fade when promise runs. Here is the sample code
Everything fades away except this field
while the promise is running. User can still type something in that box while it has to wait for promises to get resolved. Tried changing the placement of the cg-busy directive but it doesn't resolve the problem. Wondering if angular.js version matters here? Can anyone help or provide me some details related to this issue?
The text was updated successfully, but these errors were encountered: