ibolmo/mootools-core — pull request #13 by SergioCrisostomo (2014-02-28 19:04:57+00:00)
Title: fix specs to look for correct behaviour since 1.3

I have been looking at this (broken) spec and found out a weird thing.

If I do `$$(elementA, elementB).length` I get different results in different Mootools versions:
(__[jsFiddle](http://jsfiddle.net/EeDp6/)__)

1.3.2|1.2.6| 1.3.2 compat | 1.4.5 | 1.4.5compat | nightly
------|-------|------------------|--------|-----------------|---------
__0__ (strange)| 6|6 | 2 | 6 |6

Which one is right?

Looking at the source code I see a BC break between 1.2 and 1.3 __[here](https://github.com/mootools/mootools-core/blob/1.3.2/Source/Element/Element.js#L336-L358)__

The current code seems to be the same as it was in 1.3.2.

Looking at the [current source for `Elements`](https://github.com/mootools/mootools-core/blob/master/Source/Element/Element.js#L116-L127) I would say the length from above should be `2`.
I confirmed with doing a `console.log(new Elements([old, cloned])` inside the Spec [and it gave](https://gist.github.com/SergioCrisostomo/220ab66b948b15993042) as expected `2`.

----

My first conclusion is that this Spec should be `.toEqual(2);` not `6`, and just run when `no compat`
The Spec just before this is correct with `.toEqual(6);` because 1.2 behaved differently.