[Building Sakai] Fwd: IE 9 has been released
Steve Swinsburg
steve.swinsburg at gmail.com
Thu Mar 17 16:14:22 PDT 2011
Hi Noah,
Looks good to me. Is this the same process for upgrading FCKeditor in the older distro's of Sakai?
cheers,
Steve
On 18/03/2011, at 5:24 AM, Noah Botimer wrote:
> Steve and Matt,
>
> Please check out the docs and provide feedback or edits:
>
> https://source.sakaiproject.org/svn/reference/trunk/library/src/README-ckeditor-upgrade.txt
>
>
> I think the upgrade to 3.5.2 is complete for trunk and 2.8, but needs to be tested:
>
> https://jira.sakaiproject.org/browse/SAK-20296
>
>
> I have not looked at adding the headers or properties.
>
> Thanks,
> -Noah
>
> On Mar 16, 2011, at 5:59 PM, Steve Swinsburg wrote:
>
>> Thats what I was getting at about the docs. What needs to be modified from a version of FCK/CKEditor that I can download from their web site, ie config.js etc in order to plug it in to Sakai.
>>
>> If the 2.6 FCKEditor is broken in IE9 we will want to upgrade as well, if that is possible.
>>
>> cheers,
>> Steve
>>
>>
>> On 17/03/2011, at 6:02 AM, Noah Botimer wrote:
>>
>>> I totally agree about the header option. Whether it's through a generic or specific property, it should be switchable.
>>>
>>> The readme is a great idea. I tried really hard to make sure that it's just a drop-in. Our FCKeditor integration has some tweaks in the directory and, having upgraded it a time or two myself, know that it was a mysterious process (e.g., should I try to make a patch available?).
>>>
>>> Thanks for the nudge -- I'll pay specific attention to the upgrade process and try to get some notes into the source tree and Confluence.
>>>
>>> Thanks,
>>> -Noah
>>>
>>> On Mar 16, 2011, at 2:54 PM, Matthew Jones wrote:
>>>
>>>> Thanks Noah, I agree that the header fix should be the default for 2.8, but there should also be an easy way to disable it without modifying code. I'd put this at a blocker and probably also look to getting a the next release of 2.7 out for this too. It's going to be a bigger problem as more people upgrade. (Even if it is just a few % of the users)
>>>>
>>>> My only point about CKEditor was that it would be nice if there was some kind of sakai-upgrading-readme.txt that gave some hints if the next person (not you) decided they wanted to try to upgrade CKeditor. Just some tips that might help them. Can I just unpack the new source and do an svn commit? Do I have to update some config files? Are some files custom? Should I make a new directory (ckeditor-3.5.2) and not overwrite it. Just don't want to spend time duplicating work. My interest goes up as time progresses. ;)
>>>>
>>>> On Wed, Mar 16, 2011 at 2:30 PM, Noah Botimer <botimer at umich.edu> wrote:
>>>> Just an FYI to the list...
>>>>
>>>> I'm looking at bumping CKEditor up today. It's later than usual for 2.8, and I apologize for not staying on top of this, but I think IE9 compatibility has to be a priority for 2.8.0/2.8.1. Whatever our personal browser choices are, we cannot ignore the default browser of the majority of the OEM market.
>>>>
>>>> Also, please note that I don't feel special ownership of the CKEditor integration. I would certainly welcome additional help and monitoring. Talk to me if you're interested.
>>>>
>>>> As a last note, the CKEditor support is still beta/experimental and, while available for 2.8, is not the default. It works pretty well, but it needs more real world testing, documentation, and to be allowed to progress on the maintenance branch to grow healthily and be useful.
>>>>
>>>> All of this means that the header fix is not optional. It should be in for 2.8.0. We can't crutch on the CKEditor support yet.
>>>>
>>>> Thanks,
>>>> -Noah
>>>>
>>>> On Mar 16, 2011, at 10:42 AM, Matthew Jones wrote:
>>>>
>>>>> There is no fix for the FCKEditor except compatibility mode. The fix for CKEditor (if we're on an older version) is to upgrade. I don't know if Noah wrote any docs which would assist in an upgrade of CKEditor. I know were have installed 3.4.1, which is before the version where they claim to have made IE9 specific fixes.
>>>>>
>>>>> The fix will be to the request filter like in SAK-16074 but the default this really should be configurable with properties. I just wasn't sure if it was worth the quick single property fix for now, or doing it right so other headers could be set easily set on the response.
>>>>>
>>>>> It might be could adding a property like
>>>>> requestfilter.header,X-UA-Compatible="IE=EmulateIE8"
>>>>>
>>>>> And someone could potentially leave it blank and the header wouldn't be set.
>>>>>
>>>>> Otherwise we could have something like:
>>>>> requestfilter.header.names.count=1
>>>>> requestfilter.header.names.1="X-UA-Compatible"
>>>>>
>>>>> requestfilter.header.values.count=1
>>>>> requestfilter.header.value.1="IE=EmulateIE8"
>>>>>
>>>>> -Matthew
>>>>>
>>>>> On Wed, Mar 16, 2011 at 8:46 AM, Steve Swinsburg <steve.swinsburg at gmail.com> wrote:
>>>>> Are there any docs on what needs to be modified in FCK/CKEditor to make it work with Sakai, so that upgrades can be done more regularly?
>>>>>
>>>>>
>>>>> cheers,
>>>>> Steve
>>>>>
>>>>>
>>>>>
>>>>> On 16/03/2011, at 9:55 AM, Matthew Jones wrote:
>>>>>
>>>>>> Also, I'm not sure what version of CKEditor was implemented for 2.8 but on 16 Feb 2011 they released a special version of CKEditor because of IE9 as well. So that code may need some updates (or the compatibility mode fix also)
>>>>>>
>>>>>> http://ckeditor.com/blog/CKEditor_3.5.2_released
>>>>>>
>>>>>> On Tue, Mar 15, 2011 at 4:01 PM, Mathieu Plourde <mathieu at udel.edu> wrote:
>>>>>> Hi guys,
>>>>>>
>>>>>> I have confirmed that this bug is present in our Sakai instance for users of IE9 at Delaware (2.6.3). I made the the following screenshots for anyone to use.
>>>>>>
>>>>>> Freezed up: http://www.flickr.com/photos/mathplourde/5529392273/
>>>>>>
>>>>>> Compatibility mode enabled: http://www.flickr.com/photos/mathplourde/5529980226/
>>>>>>
>>>>>> Mathieu
>>>>>> =================================
>>>>>>
>>>>>> Mathieu Plourde, MBA
>>>>>> Project Leader, LMS/Instructional Designer
>>>>>> IT-Client Support & Services
>>>>>> mathieu at udel.edu
>>>>>> Office: 302-831-4060
>>>>>>
>>>>>> =================================
>>>>>>
>>>>>> TOP LINKS:
>>>>>>
>>>>>> Technology Troubleshooting: http://www.udel.edu/help
>>>>>> Sakai at UD Support and Training: http://www.udel.edu/sakai/training
>>>>>>
>>>>>> =================================
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Mar 15, 2011 at 12:58 PM, Matthew Jones <jonespm at umich.edu> wrote:
>>>>>> Well, I was briefly testing it out with the final release of IE9.
>>>>>>
>>>>>> The "good news" is that the FCKEditor does come up, so at least the text areas are usable. The bad news is that almost everything that pops up a window freezes the browser. So this is not a good thing. Compatibility mode fixes this.
>>>>>>
>>>>>> I might continue to briefly look at it but our best fix will be to patch in that meta tag. I'll add it in so it can be set via property (which version to emulate) or disabled if desired. By default we'd probably have it configured to emulate IE8.
>>>>>>
>>>>>> 1 minute screen cast demoing the FCK bug in the current version of IE9.
>>>>>> http://www.screencast.com/users/jonespm/folders/Jing/media/030b170e-87f1-4b1f-a337-fb00cfd08bab
>>>>>>
>>>>>> -Matthew
>>>>>>
>>>>>>
>>>>>> On Tue, Mar 15, 2011 at 11:14 AM, Berg, Alan <A.M.Berg at uva.nl> wrote:
>>>>>> I plan QA to test IE 9 in the coming days. I have already suggested to Rob and Corey to focuss the next test fests in this direction..
>>>>>>
>>>>>> Matthews compatability patch seems the way to go in the short term. If that gets in before the next RC we may have just about enough run up time to verify.
>>>>>>
>>>>>> Alan
>>>>>>
>>>>>> Alan Berg
>>>>>> QA Director - The Sakai Foundation
>>>>>>
>>>>>> Senior Developer / Quality Assurance
>>>>>> Group Education and Research Services
>>>>>> Central Computer Services
>>>>>> University of Amsterdam
>>>>>> From: sakai-dev-bounces at collab.sakaiproject.org [sakai-dev-bounces at collab.sakaiproject.org] on behalf of Matthew Jones [jonespm at umich.edu]
>>>>>> Sent: 15 March 2011 16:01
>>>>>> To: markjnorton at earthlink.net
>>>>>> Cc: sakai-dev
>>>>>> Subject: Re: [Building Sakai] Fwd: IE 9 has been released
>>>>>>
>>>>>> Yea, I saw the announcement last night. The IE9 release candidate completely broke FCKEditor and they weren't expected to fix it. This would make anything earlier than 2.8 (since 2.8 had a CKEditor option) mostly unusable by default. I was going to find a Windows 7 machine today (since it won't install in XP) and see if there are still these big problems. If they weren't fixed in the final release is we'd probably need to patch in a IE8 compatibility patch for all of the releases that are using this editor.
>>>>>>
>>>>>> https://jira.sakaiproject.org/browse/SAK-20058
>>>>>>
>>>>>> -Matthew
>>>>>>
>>>>>> On Tue, Mar 15, 2011 at 10:51 AM, Mark Norton <markjnorton at earthlink.net> wrote:
>>>>>> This seems to be worth cross-posting. Hopefully it doesn't complicated the QA work on Sakai 2.8.0.
>>>>>>
>>>>>> - Mark
>>>>>>
>>>>>> -------- Original Message --------
>>>>>> Subject: IE 9 has been released
>>>>>> Date: Tue, 15 Mar 2011 10:04:03 -0400
>>>>>> From: Justin Obara <obara.justin at gmail.com>
>>>>>> To: fluid-work Work <fluid-work at fluidproject.org>
>>>>>>
>>>>>> Internet Explorer 9 was just officially released.
>>>>>> http://www.microsoft.com/presspass/presskits/internetexplorer/
>>>>>>
>>>>>> This means that as of Infusion 1.4 we will be tracking it as an a-grade browser in Windows 7. I've upgraded our browser support chart to reflect this.
>>>>>> http://wiki.fluidproject.org/display/fluid/Browser+Support+Chart
>>>>>>
>>>>>> Please make sure that you are periodically testing with IE 9. Also please ensure that any pre-release versions of IE 9 are upgraded to the latest stable release.
>>>>>>
>>>>>> Thanks
>>>>>> Justin
>>>>>> _______________________________________________________
>>>>>> fluid-work mailing list - fluid-work at fluidproject.org
>>>>>> To unsubscribe, change settings or access archives,
>>>>>> see http://fluidproject.org/mailman/listinfo/fluid-work
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> sakai-dev mailing list
>>>>>> sakai-dev at collab.sakaiproject.org
>>>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>>>>
>>>>>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> sakai-dev mailing list
>>>>>> sakai-dev at collab.sakaiproject.org
>>>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>>>>
>>>>>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> sakai-dev mailing list
>>>>>> sakai-dev at collab.sakaiproject.org
>>>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>>>>
>>>>>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> sakai-dev mailing list
>>>>> sakai-dev at collab.sakaiproject.org
>>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>>>
>>>>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20110318/a3d693cf/attachment.html
More information about the sakai-dev
mailing list