Thanks Sean, but sooner or later I'll need to update my scripts anyway. I think most of them will need little to no changes, I just need time to test everything and make sure everything is working fine. Besides that, I know that newer versions brings improvements, Slick being one of those, and by updating I'll only have benefits.
I'll test again tomorrow, probably I did something wrong friday. Asking for a last favor, there is a list of changes between versions? I can't find them :( On 12 dez, 00:47, Sean McArthur <[email protected]> wrote: > If its a pain converting everything to 1.3, you could try just switching > 1.2's selector engine to use Slick. > > I'm sure David Walsh has blogged about how to do that. > > Sean McArthur > On Dec 11, 2010 9:19 AM, "Tyk" <[email protected]> wrote: > > > Well, that's really strange. I'm home now, but monday by the morning > > I'll test it again. I'm sure that I tested with both versions with > > identical results. > > But in the jsfiddle provided by Sanford (thanks), everything works > > fine. > > > Anyway, working or not, I'll report back when I test it again. Problem > > is, I have a lot of code made for mootools 1.2, and the 1.3 > > compatibility layer adds some weight to the script. Maybe this is a > > good reason to review and alter my classes and functions. > > > Thanks! > > > On 10 dez, 23:32, Sanford Whiteman <[email protected]> > > wrote: > >> > I'm still using 1.2.4 version, but this happens with 1.3 too. > > >> Are you sure? You should get out-of-document-order results with 1.25 > >> but not from 1.3. > > >> http://jsfiddle.net/XCPdb/(switchthe Moo version to compare) > > >> Taking getElements as a backward-compatible implementation of > >> querySelectorAll, results should be returned in DOM order regardless > >> of the order of the selectors in the selector string (as with native > >> qSA). > > >> -- Sandy
