Thank you, I confirm the new build works fine for the issue described above.
Anyway, I'm quite worried. I mean, v1.4.3 had the getProperty problem that crashed my programs. v1.4.4 has this new problem. Maybe I'm not so lucky, but I use mootools since about 2005 and never had these kind of issues. Mootools already suffers (yes, far less than some years ago, but..) of some kind of retro-compatibility problems. That's one of the main reasons (or excuses) people often give for using JQuery instead. For me, it's not a problem at all because I think mootools is by far best than jquery, at least for me as a programmer. BUT, IF official 'stable' releases start to have too bugs of this kind, that maybe starts to be too much for me, because I need to trust the framework, and I'm worried. Anyway, as I said above, it's the first time it happens (at least to me). So, have you had some unusual problems in your devs team maybe? Regards On 13 Feb, 19:40, Arian Stolwijk <[email protected]> wrote: > We have probably fixed this already, but are still testing the new release > to prevent bugs like these to make sure we will have a stable release. > > We would appreciate if you would test it for your purpose and tell us if > it's fixed for you. > You could > usehttp://mootools.net/nightly/build/mootools-core.jsorhttps://github.com/mootools/mootools-core/wiki/Build-MooTools-from-gi... > > Tanks for your patience. > > > > > > > > On Mon, Feb 13, 2012 at 6:36 PM, stratboy <[email protected]> wrote: > > Hi! I'm quite sure i've just found a bug: > > >http://jsfiddle.net/stratboy/xqems/ > > > That works. But if I use the 1.4.4 core (can't do it in jsfiddle..) > > the second transition (opacity 1 to 0) doesn't work. Instead, it sets > > suddenly opacity to 0 without any transition. > > > By the way, that's not a real class.. It's something I'm starting with > > to build a more complex fx > > > Bye!
