Community
Participate
Working Groups
Dojo 1.6 has been released. It fixes some IE9 browser detection bugs (see [1]) that we're currently using <meta http-equiv="X-UA-Compatible" content="IE=8"> to work around. Opening this bug to discuss upgrading to 1.6. [1] http://bugs.dojotoolkit.org/ticket/12243
About the content="IE=8" workaround: at one point there was a problem with the editor's inner IFRAME when the outer document was running in IE9 mode -- see Felipe's comment in Bug 334041. Should find out if this is still an issue.
(In reply to comment #1) > About the content="IE=8" workaround: at one point there was a problem with the > editor's inner IFRAME when the outer document was running in IE9 mode -- see > Felipe's comment in Bug 334041. Should find out if this is still an issue. Yes, that is still an issue.
We definitely want to move to 1.6. We just need someone familiar with the dojo subsetting to help package something up to submit in ipzilla. Another big change is support for HTML5-compliant attribute tags. For example replacing jsId references with data-dojo-id, etc. This would allow our HTML to be fully HTML5 compliant.
> Yes, that is still an issue. I lied, the bug no longer exists, you should be able to remove the <meta http-equiv="X-UA-Compatible" content="IE=8"> Just wait till we release bug 341270 as it has some good performance improvement we can use in IE9.
I've removed this header from all of our files now to go along with the move to Dojo 1.6.1. I left the code in editor.js that will downgrade to ie7 mode for ie<9 as that still makes sense in some contexts.