[cle-release-team] [sakai2-tcc] IE9 Compatability in 2.9

[Noah Botimer]

I'm not sure that the flag was a stop-gap to a given release. I would say that it was a stop-gap until there was sufficient QA to track down IE8/9-related issues and make the upgrades/fixes.

For now, I think your concern about LTI is valid -- at last check, iframes inherit the parent's compatibility mode.

So, I agree. Although we might elect in the waning moments of the 2.9 cycle to keep the compatibility header, we probably should turn it off to get the most IE9 QA traffic we can. But testers should be aware of and use the browser setting to behave like IE8/IE7 so we can isolate those issues as such.

Please also note that good IE (browser) issue analysis is a pretty difficult skill set to enroll, requiring the right tools and knowledge to make helpful reports. Tickets like "page X of tool Y doesn't work in IE9" are better than nothing, but we really need more detail like whether there were script errors, etc. Just things to think about as folks track these down.

Thanks,
-Noah

On Oct 7, 2011, at 4:23 PM, May, Megan Marie wrote:

> Compatibility mode was supposed to be the stop-gap until 2.8.1 was released.    Given that we are in the beginning of the 2.9 release cycle, this seems like a perfect time to a) identify problems and b) fix them.  With more and more integrations occurring with BLTI I’m going to guess that some of those other systems might need the latest version of IE.   
>  
> Also, did we ever resolved all the IE8 had issues?
> Megan
>  
> From: jonespm at gmail.com [mailto:jonespm at gmail.com] On Behalf Of Matthew Jones
> Sent: Friday, October 07, 2011 4:10 PM
> To: May, Megan Marie
> Cc: cle-release-team at collab.sakaiproject.org; sakai2-tcc Committee
> Subject: Re: [cle-release-team] IE9 Compatability in 2.9
>  
> From what I remember, the major problem with IE9 was FCKEditor was broken and never getting fixed. Since we've upgraded to CKEditor that would be resolved. However I know that we're still running in compatibility mode so I doubt anyone has tested with the "real IE9".
>  
> So yes, trunk is still forcing compatibility mode, we probably could do without it, but QA would probably discover new things to fix in our code that we could fix.
>  
> I have not tested with the IE10 developer preview, but know that the compatibility flag still works. If there isn't anything that *needs* IE9 specifically and it all works in IE8 compatibility mode, I'd say we just wait until 2.10 or 2.9.1 to address this and mark it as a lower priority?
>  
> (default.sakai.properties)
> sakai.X-UA-Compatible=IE=EmulateIE8
> https://source.sakaiproject.org/svn/config/trunk/configuration/bundles/src/bundle/org/sakaiproject/config/bundle/
>  
> On Fri, Oct 7, 2011 at 4:03 PM, May, Megan Marie <mmmay at indiana.edu> wrote:
> Good afternoon,
>         I haven't been able to attend the last few release meetings so please forgive me if this has been discussed.
> 
> Where are we as a community at ensuring the IE9 is going to be supported for this release?    For instance, is trunk forcing compatibility mode?
> 
> Megan
> 
> 
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>  
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20111013/1a0815fd/attachment-0006.html