-
Notifications
You must be signed in to change notification settings - Fork 51
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
Message doesn't fully disappear #34
Comments
Yes, this is true, there is a bug and the solution above will fix it. Unfortunatelly, if there is a close-button <button ....>
then button won't disappear too :-) |
Hi @ericmcgregor, Have you tried out https://github.com/wmluke/angular-flash#styling-considerations to resolve the visibility issues? Thanks, |
I was trying to use styling considerations with "alert in" classes, but did not work for me. Or I missed something perhaps... Actually, in the examples, there is no hiding CSS styling (something like alert .close {display: none} or similar) - so I'd say it's either incomplete or not really functional. |
It doesn't really work, indeed. The dismissed alert still takes up place for an unknown reason; the classes seem correct though. |
@ericmcgregor You could also set the display CSS property on the flash message container to "none" and then set the "active class" ("in" by default) display property to "block", "inline", etc.. Then you wouldn't have to add code to clear flash.message. |
Same behavior here, @ericmcgregor solution works for me! |
same here |
Hey, great little service! I did notice that the message continues to take up space in the dom after it is 'closed'. This seems to be because inside the directive you are leaving the message object on the scope instead of clearing it out.
If you add $scope.flash = {} to the flash-directive on line 26 it'll fix it.
The text was updated successfully, but these errors were encountered: