Are they going to at least alias the opacity filter to actually support the real opacity standard? How many other MS-CSS filter properties mirror actual CSS standards properties?

Are we going to see exposure Element and Node (and their associated prototypes) and all of the other DOM abstracts that are needed for high end development? Need I mention the performance and memory improvements you gain by not having to manually extend every element in the DOM?

Are they actually going to treat XHTML (and preferably HTML also) as an XML based language so that XPath and inserting XML nodes etc actually works?

Will we see any of the newer JS standard functions (Array.forEach etc)?

Why is it that every JS library developer can manage to get full CSS3 selector support, yet MS cannot? Why waste everyones time with the selectorQuery function and then do it halfway?

Is getElementsByTagName(‘*’) going to continue to return a text node (DOCTYPE?!?!?!) as the first item?

Are they going to fix arrays so that numbered arrays that have a named property added don’t return a type of string when for the key when a numbered element is accessed?

Are they finally going to get rid of all of the peek-a-boo bugs (yes they still happen in 7)?

Events!?!?!? go figure

It is fantastic that they are going to have support for more standards (MathML, SVG etc). Why don’t they get the basics fixed before they try to jump the gun on emerging standards and screw those up also? Or is this another attempt to subvert emerging standards to MS incompatible standard before the real standards can solidify?

Sorry, for the rant all, this is in no way trying to shoot the messenger. Great job in letting the world know what is going in with IE8. Hopefully, MS’s new “transparency” will allow people to get answers on whether IE8 will actually be a fix to their existing shortfalls or just a broken implementation of new and old standards.

Plus it does not apply styles to xhtml I dynamically added in my page using prototype’s “Insertion.Bottom()” (aventried After(), Top() or Before()…). Maybe it’s just that Prototype needs to be updated for IE8… I dunno…

I guess the Acid test is not the end-all of tests when it comes to making sure you are CSS 2.1 compliant… and right now I very much doubt that IE8 actually is …

I thought what they meant was “We passed it”, “Now we no longer have to worry about it”…. good to see the continued push towards REAL OPEN standards Microsoft. Keep it up.