Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 341270

Summary: [client][editor] Support IE 9 for the Editor
Product: [ECD] Orion Reporter: Felipe Heidrich <eclipse.felipe>
Component: ClientAssignee: Silenio Quarti <Silenio_Quarti>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3    
Version: 0.2   
Target Milestone: 0.2   
Hardware: PC   
OS: Windows 7   
Whiteboard:
Bug Depends on:    
Bug Blocks: 340665    

Description Felipe Heidrich CLA 2011-03-29 14:29:18 EDT 
Background information:

An IFRAME inside of IE9 (doctype9) can either be doctype9 or quirksmode (for example, you can't have a top page doctype 9 with a iframe with doctype8).

Here is the doc
http://blogs.msdn.com/b/ie/archive/2011/03/24/ie9-s-document-modes-and-javascript.aspx
this table explain it better:
http://ieblog.members.winisp.net/misc/How%20IE9%20Determines%20Document%20Mode.svg

and unfortunately early (beta) version of IE9 had a bug that prevent the editor from running on IE9. See
https://connect.microsoft.com/IE/feedback/details/620632/iframe-set-to-backcompat-when-contentdocument-accessed-after-creation 

For that reason the page embeding the editor had to be set to IE8:
<meta http-equiv="X-UA-Compatible" content="IE=8"/>
(IE8 allows the iframe to be what ever doctype it wants http://blogs.msdn.com/b/ie/archive/2010/03/02/how-ie8-determines-document-mode.aspx)

Internally the editor would not run with doctype8, mostly because of performance. Instead, the iframe for the editor was set to doctype7.


The final release of IE9 no longer has the bug the prevent us before.

This bug is intent to document the changes on our usage of the doctype and make sure the editor works well on IE9 (using the all the new APIs when it makes sense).