 |
 |
OK, but that begs the question of, why should the user have to go through such contortions in the first place? Shouldn't any web system be designed to follow well-established standards in the first place, so that it works with modern browsers? If a system works with older browsers, and newer browsers still run the old code, then shouldn't a system just work with newer browsers without any fuss? And if so, shouldn't that system *not* include code to specifically and arbitrarily exclude newer browsers? Like others, I find this simply unacceptable. I would be ashamed to release such a system myself. -- dkm At 6/23/2011 03:43 PM Thursday, Rytlewski, Jamie wrote: >It's not that they can't use EBS if they upgrade, they just have to >use compatibility mode (withIE). It's really not that difficult to >use compatibility mode. Yes, you have to show your users how to do >it, but I've had no problem in my office. > >On Jun 24, 2011, at 4:40 AM, Kim Geiger wrote: > > >>>> On 6/23/2011 at 3:29 PM, Troy Murray <[log in to unmask]> wrote: > > > >> I agree with you about the lack of support for newer browsers, the > >> Angel/Blackboard system has the same limitation. > > > > I was just grumbling about this this morning. Yes, it's true > that I don't understand the nature of the problem behind the > scenes, but if I encountered it at Amazon or elsewhere, they'd lose > a sale rather than get my sympathy. > > > > It's kind of, well, unacceptable, actually, and it's turning into > a real support hassle for me as my users, despite my admonitions, > click on the upgrade button and then can't use EBS. > > > > -- > > Kim Geiger > > Information Technologist > > Broadcasting Services > > Michigan State University > > 517-432-3120 x 429