Echo Web Framework

11.1 You retain copyright and any other rights you already hold in Content which you submit, post or display on or through, the Services.By submitting, posting or displaying the content you give Google a perpetual, irrevocable, worldwide, royalty-free, and non-exclusive license to reproduce, adapt, modify, translate, publish, publicly perform, publicly display and distribute any Content which you submit, post or display on or through, the Services. This license is for the sole purpose of enabling Google to display, distribute and promote the Services and may be revoked for certain Services as defined in the Additional Terms of those Services.

Hello,

I'm the lead developer of the Echo web application framework. I'm seeing major issues with IE8's rendering of Echo-based applications when "compatibility mode" is not enabled. These applications work in literally every other browser market, e.g.:

- Opera
- Mozilla/Firefox 1.0-current
- Safari 1.3-current
- IE6, IE7
- Konqueror
- Google Chrome

Great care has been taken in developing the Echo platform such that it respects all W3C specifications for HTML, CSS, and DOM manipulation, in addition to following the ECMA-262 v3 scripting spec. It supports all of the above browsers quite well (running in the most standards compliance mode each has to offer) using a single codebase with only minimal browser specific workarounds (most of which target IE6).

I'm seeing major issues with IE8. Significant manipulations of the DOM result in the entire screen turning white, with elements that moments before had "clientWidth" values of say 1000 suddenly having values of 0 even though they have not been modified. Scrollbars jump to the top within DIVs after trivial CSS manipulations (e.g. rollovers). CSS attributes are sometimes simply not rendered, or only show up in wierd circumstances, such as when a user is highlighting text.

An example of the issues can be seen here: http://demo.nextapp.com/echo3csjs

Click the pull down menus or press any button within it for an example of the disappearing content. You can see for example the clientWidth changing by visiting the following URL...

javascript:alert(document.getElementById("rootArea").firstChild.clientWidth);

....when the echo3csjs demo URL above is being displayed, before/after the disappearance occurs.

This application is written entirely in JavaScript, HTML and CSS, the source can be viewed or downloaded with a Subversion client from https://svn.nextapp.com/svn/echo3demo/trunk/

I'd be happy to help in any way I can, short of spending days trying to reproduce these bugs in standalone test cases. :D

Please feel free to email me if you want to discuss this further, tliebeck (at) nextapp (dot) com.

Best
--Tod Liebeck / NextApp, Inc.