[Using Sakai] [Building Sakai] Support for additional browsers

[Steve Swinsburg]

We have a browser check page which scans the browser and its capabilities and gives you a report. Could have a similar one for Sakai perhaps. It's just HTML and JS:
https://login.anu.edu.au/browsercheck/

cheers,
Steve

On 02/04/2011, at 2:44 AM, Mathieu Plourde wrote:

> Hi David,
> 
> I agree with your statement. You could probably use the same popup principle to notify your users when a new browser version comes up not to upgrade right away, with a link to download to the most recent locally certified version.
> 
> I'll let other folks jump in with info about the status of QA for specific browser versions.
> 
> 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 Fri, Apr 1, 2011 at 11:30 AM, David C. Minugh <David.Minugh at english.su.se> wrote:
> Dear Mathieu,
> 
>   Your screenshot is pretty much the sort of thing we need to know, but it's post hoc: "you can't see Sakai because you've trying to use browser X (version Y)". I was thinking of an early-warning, "Don't install browser X (version Y) yet, because we're not yet able to fully support it". This seems to be the current case for IE9, which has been available for several weeks already.
>   But I do want to emphasize that I see it as the individual school's job to warn their students and staff away from upgrading to versions with known blockers.
> 
> 
> 
> On 2011-04-01 15:58, Mathieu Plourde wrote:
> Hi David,
> 
> Blockers for each release are listed in Jira, but the end-user wouldn't know that.
> 
> We have had issues with Chrome and Safari users since the very beginning. This year, we decided to add a warning prompt for users of these browsers (see screenshot). We didn't get too much pushback so far.
> 
> http://www.flickr.com/photos/mathplourde/5579097179/
> 
> So this is an example of an early warning system as implemented institutionally at the University of Delaware. Is that what you had in mind? This is something that's really easy to deploy and that seems to have cut down of browser-related issues for us.
> 
> Mathieu
> 
> -- 
> 
> David C. Minugh                                 E-mail: David.Minugh at english.su.se
> Director of Studies                             Tel: (+46) 8 16 36 11
> English Department                              Cell phone: (+46) 70 - 23 14 777
> Stockholm University                            Office: E 877, Frescati
> 
> 
> _______________________________________________
> 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-user/attachments/20110404/a51408e9/attachment.html