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
Currently, remote content, unless loaded really quickly, or already cached in-browser, will not always show the (CSS) transitions, which is a nuisance. This is because the transition "starts" using an empty DIV, and often the content hasn't arrived until after the div has already been "transitioned" in.
I have a Pull Request with a fix, however it currently is failing on the @twbs-savage test, it errors with a 10 minute timeout in trying to connect. Is this an issue with the continuous-integration process, or the code itself?
In any case, I'm not tied to this particular solution presented in the Pull Request, but I figured it'd be valuable to not only supply a "complaint" but also a way to fix it! If there's a different preferred implementation that fixes the root issue, I'm certainly open to it.
The text was updated successfully, but these errors were encountered:
The remote option is deprecated (see http://getbootstrap.com/javascript/#modals-options & #14034) and Bootstrap v3 is in maintenance mode at this point so we can focus on v4.
Since the issue isn't a showstopper and concerns a deprecated feature, I'm calling this WontFix. Sorry!
Currently, remote content, unless loaded really quickly, or already cached in-browser, will not always show the (CSS) transitions, which is a nuisance. This is because the transition "starts" using an empty DIV, and often the content hasn't arrived until after the div has already been "transitioned" in.
I have a Pull Request with a fix, however it currently is failing on the @twbs-savage test, it errors with a 10 minute timeout in trying to connect. Is this an issue with the continuous-integration process, or the code itself?
#18274
In any case, I'm not tied to this particular solution presented in the Pull Request, but I figured it'd be valuable to not only supply a "complaint" but also a way to fix it! If there's a different preferred implementation that fixes the root issue, I'm certainly open to it.
The text was updated successfully, but these errors were encountered: