Thank you Sanford, your method seems to work just fine, but I tested the code with 1.3 again and it's working now (don't question why it doesn't worked last week), and now I'm updating everything. I downloaded the new version without compatibility, since I'll need to review all scripts anyway, let's make it right from the start.
To anyone who may need a guide to update, I found this: https://github.com/mootools/mootools-core/wiki/Upgrade-from-1.2-to-1.3 The only thing that bugs me is the Browser.engine being deprecated. It's almost okay if I only want to work with basic recognition of the most used browsers, but what happens with all the other webkit based ones? And if I need to make things compatible with browsers using the same engine but with different versions? I have a lot of workarounds based in the engine used by the browser, and I'll need to find a workaround to make my workarounds work :P :P On 13 dez, 00:24, Sanford Whiteman <[email protected]> wrote: > As a patch before you move to Slick where everything is already in > document order, here's a function to resort an array of elements into > document order even if you are using Moo 1.2x. > > http://jsfiddle.net/XCPdb/3/ > > To sort it uses either > > · `sourceIndex` reflection property in IE > > · the standard `compareDocumentPosition` method in DOM 3 browsers > > · querySelectorAll for the rest, such as Safari 3.x > > The first two are thanks to a well-circulated article by PPK, while > the final fallback may or may not be my own invention. > > -- S.
