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

[Noah Botimer]

I think this is the most important point, here: the "list" hasn't been reevaluated in quite a while. The list represents our collective, spoken intent to test a given set for a release. This should be because it reflects the reality of our user base and, thereby, what is important to us.

We know the reality is that some things will get fixed whether or not a given browser is on a list, and some things won't, despite being on a list. What's important is that, during our QA process, we ask things like "how is X coming along?" and have a known record of test results. A bunch of anecdotal reports and fixes on the side don't help us to know where we really are as a community. It's about structure for the information.

Even with all of the positive results from Safari and Chrome testing, and the fixes happening, there is no documented understanding of these (except maybe by trawling mailing list archives and JIRA).

This is the long winded version of: Lance, you are absolutely right on.

Thanks,
-Noah

On Mar 31, 2011, at 3:50 PM, Speelmon, Lance wrote:

> Sorry if you have heard me say this before, but as a community we should not be talking about which browsers are "supported" - we do not provide support.  As already stated, bugs get reported against browser x.y.z and bugs get fixed.  Instead, we should be talking about which browsers were used to QA a release and thus how much capacity QA has to test N number of browsers.  
> 
> I am fine with local institutions and commercial partners framing the discussion around support - that is what they do.  As a community, we should be transparent about the QA process and which browsers were used in testing.  WDYT?  Thanks, L
> 
> On Mar 30, 2011, at 2:59 PM, Mathieu Plourde wrote:
> 
>> Dear fellow Sakaigers,
>> 
>> The use of Mac computers on our campus has grown dramatically over the last few years, and as a result many faculty and students would like to be able to use the Safari browser when using Sakai. The popularity of all iOS devices which rely on Safari also makes a case for making Sakai compatible with Sakai. Many features do work successfully in Sakai on this browser, but unfortunately there are several instances where unexpected behavior can occur and so we are compelled to warn our users, and request that Safari not be used with Sakai.
>> 
>> Similarly, Chrome has recently been rated as the third most used browser behind Internet Explorer and Firefox. Since Chrome, Safari, and many mobile device browsers are based on the Webkit engine, once we make one of them compliant, we may find that it is relatively easy to make Sakai work with others. [1]
>> 
>> This is not the first time that such a call to action has circulated on-list, but we believe that it is time to rethink our Firefox-centric approach, not only for Sakai OAE, but for the 2.x branches as well.
>> 
>> Any thoughts or progress on these fronts?
>> 
>> [1] http://gs.statcounter.com/#browser-na-monthly-201003-201103
>> 
>> =================================
>> 
>> 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
>> 
>> =================================
>> _______________________________________________
>> 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-user mailing list
> sakai-user at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-user
> 
> TO UNSUBSCRIBE: send email to sakai-user-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/20110331/59830fc8/attachment.html