That is to say that this has been brought up before, but was forgotten again. It seems like a reasonable idea for most of the show/hide animations, but I'm not entirely sure if it's as simple as you make it out to be. Some users may rely upon the current behavior, and changing that will effect their applications.
--John On 3/15/07, John Resig <[EMAIL PROTECTED]> wrote: > Could you create a ticket for this? Otherwise it's just going to get lost. > http://dev.jquery.com/ > > --John > > On 3/15/07, Daemach <[EMAIL PROTECTED]> wrote: > > > > I'm working with the fade and slide animations now, and while testing I've > > hit a couple of points where an element tried to slideIn when it was already > > ... in, and fadeOut when it was already...out. In both cases the animation > > starts from the beginning, fully hiding the element and sliding it in or > > showing the element and fading it out. Now I know I can handle it in my > > code, but the behavior seems a little less intelligent than it could be. If > > someone calls a fadeout function the end result is display:none - likewise > > for a slideup. Therefore, if the element style is already display:none the > > function is technically successful. Can this check be worked into the core > > logic? It would make the library feel smarter. > > > > Dealing with chaining animations through callbacks is already difficult > > enough for new people without having to deal with this :) > > -- > > View this message in context: > > http://www.nabble.com/Animation-question-tf3410946.html#a9503546 > > Sent from the JQuery mailing list archive at Nabble.com. > > > > > > _______________________________________________ > > jQuery mailing list > > discuss@jquery.com > > http://jquery.com/discuss/ > > > _______________________________________________ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
