All looks good in Firefox 5.0a2!

(Although it might be worthwhile extending the time that the tests wait for
iframes to load...)

http://barryvan.com.au/
[email protected]


On Sat, Apr 16, 2011 at 6:37 AM, Arian Stolwijk <[email protected]> wrote:

> If you like you can run the specs in node.js too:
>
> git clone https://github.com/mootools/mootools-core.git (or
> mootools-more.git)
> cd mootools-core (or mootools-more)
> git submodule update --init --recursive
> cd Specs/Runner
> ./runner.js
>
> I'm pretty sure they'll pass though ;)
>
>
> On Sat, Apr 16, 2011 at 12:31 AM, Arian Stolwijk <[email protected]> wrote:
>
>> Hi all!
>>
>> Currently we are testing for our new upcoming release of MooTools: 1.3.2!
>> To do this we've set up http://mootools.net/test
>>
>> If you want you can run these links in, for example, IE6 (♥) and all other
>> browsers.
>>
>> *Core:*
>>
>> http://mootools.net/test/mootools-core/Specs/Runner/runner.html?preset=core-1.3-base
>>
>> http://mootools.net/test/mootools-core/Specs/Runner/runner.html?preset=core-1.3-client
>>
>> *More:*
>>
>> http://mootools.net/test/mootools-more/Specs/Runner/runner.html?preset=more-base
>>
>> http://mootools.net/test/mootools-more/Specs/Runner/runner.html?preset=more-client
>>
>> *More Manual Tests* (most important changes: Element.Position and
>> Delegation)
>> http://mootools.net/test/mootools-ui-runner/
>>
>> *Slick*
>> http://mootools.net/test/slick/SlickSpec/Runner/runner.html?preset=slick
>>
>> *Known Specs Issues*
>> There are a few things to keep in mind:
>>
>>    - Some tests in IE for MooTools Core have some timing troubles.
>>    Because IE is slow (Fx), or some HTTP requests had to be done
>>    (Request/IFrame). Also the Function.periodical test.
>>    - One Element.Event spec is failing in IE.
>>    - IE6 and IE7 have some border collapse stuff troubles for HtmlTable
>>    - If you're in another timezone than West-Europe, some Date specs in
>>    More might be failing. Also in IE 3 Date specs fail with timezone UTC vs.
>>    GMT
>>    - Slick in Chrome has some failing nth-selector with QSA
>>
>> If you see something suspicious, or if you think everything is ok, let us
>> know, preferably with screenshots and tell what browsers/OS you tested.
>>
>> Happy Testing!
>>
>>
>

Reply via email to