Meet - ACID3

Yesterday, the famous web developer JQuery library, John Rezig, in his personal blog reported that a new, third, version of the Acid test is being prepared for release. He posted a link to the preliminary version of the network for public viewing. The author of the test reports that its development is almost complete.



Traditionally, the test checked HTML and CSS parsing. In the 3rd version, developers are guided by testing DOM and JavaScript . Let us examine what exactly is being tested, especially with regard to JavaScript:

• Array Elisia - things like [,,] should have zero length, and for array [0, ...] it should be equal to 3.
• Array methods - checks the ability to add multiple elements to an array (.unshift (0, 1, 2)) and combine it with undefined (.join (undefined).)
• Number transformations - checks the operation of such methods as .toFixed (), .toExponential () and .toPrecision (), first of all, with fractional and negative chilami.
• Operations with strings - the substr () method should be able to work with negative arguments (.substr (-7, 3)), access to the characters of the string should be done according to their position ("my string" [0]). (this is part of the ECMAScript4 specification)
• Working with dates - make sure that some methods return NaN (for example, d.setMiliseconds () with no arguments), and also that a mandatory offset of +1900 years occurs.
• Unicode characters in variable names - their use should cause an error. For example,
  

    eval ("test.i \\ u002b = 1;"); 

  
  
• Regular expressions - / [] / must match an empty array, and / []]] / cause an error. Backreference to non-existent images and negative lookaheds - /(?!test)(test).exec( test test ") should be supported.
• Enumeration - Ensure that the properties of an object are correctly listed, that properties with certain names are available (toString, hasOwnProperty, etc)
• Constructors - the user should be able to define their own constructs in the .constructor property, the .constructor property should not be in the enumeration, and the .prototype.constructor property should be removable.
• Functions - the ability to call a function by name from itself, direct change of its name should be prohibited (only using function arrays). (function test () {...}) (); - “test” should not be visible in the parent area.
• Errors - variables in the catch () {} block should work first with catch () arguments, and then with parent arguments. for example
  

   var e = "my name";
   try
   {
     ... // some code
   }
   catch (e)
   {
       alert (e);
   } 

  
  should not display "my name".
• Assignment operations - s = a.length = "123"; - a.length should return 123, not 3
• Encodings - encodeURI () and encodeURIComponent () should work correctly with zero bytes.

In general, it was a broad, but rather superficial overview of the harsh, but mandatory requirements of the ECMAScript specification. Having opened your favorite browser, you are simply doomed to find at least one of these requirements unfulfilled.
')
Details the author of the test promises to submit in the coming days.

And finally, the preliminary results of testing of UNFINISHED Acid 3 over the UNFINISHED versions of the most popular browsers that were provided by the author. We checked, it all fits together! =)

Here is the benchmark that the browser should show.



Firefox 2.x



Firefox 3.0b2



Safari 3



Webkit nightly



Opera 9.5b1



Internet Explorer 7

Related Links:

1. Preliminary mirror test.
2. Written by author John Resig in a personal blog.

Crosspost from webdev.lovata.com