I don't think it's entirely black and white though. It really depends
on the type of site and the community it serves.
What about innovative interfaces, visualizations, and apps that are
valuable resources, but simply not possible without modern browsers?
These are usually extended or experimental services and may have a
smaller user base. I think it's perfectly reasonable in that case to
let people know that they need to upgrade to join the party.
In the case of traditional services, such as the catalog, I agree that
they should just work without disclaimers.
Right, I forgot about the dreaded restaurant sites with generic ambient
loops and PDF menus. Come to think of it, that might be an iPad feature
to not display them! :)
-Shaun
On 7/12/12 3:44 PM, Aaron Collier wrote:
I'd have to agree with this, as the one time I can recall putting this kind of
message up we received complaints from faculty members.
Aaron Collier
Library Academic Systems Analyst
California State University, Fresno - Henry Madden Library
559.278.2945
[email protected]
http://www.csufresno.edu/library
----- Original Message -----
From: "Cary Gordon"<[email protected]>
To: [email protected]
Sent: Thursday, July 12, 2012 11:25:03 AM
Subject: Re: [CODE4LIB] Browser Wars
I think that anyone using IE 6 knows that they are skiing on barrel
staves. Those messages mostly piss folks off, particularly when they
are on a library site.
On the other hand, I really love getting "please update your Flash"
messages on my iPad :<P
On Thu, Jul 12, 2012 at 11:18 AM, Michael Schofield<[email protected]> wrote:
Does anyone actually generate a conditional message--say, if LTE IE7--to
suggest that visitors upgrade or otherwise warn them about a wonky site?
//Michael
-----Original Message-----
From: Code for Libraries [mailto:[email protected]] On Behalf Of Cary
Gordon
Sent: Thursday, July 12, 2012 2:11 PM
To: [email protected]
Subject: Re: [CODE4LIB] Browser Wars
While we will support anything that our clients want supported, we warn them
away from IE6 and other expensive to support antiquities. We definitely pay
attention to IE during development, as backtracking to fix an issue that has
been buried can be both depressing and expensive.
We test in Chrome, Firefox, IE, Opera, and Safari. We test Responsive and/or
mobile sites in a range of mobile clients.
Thanks,
Cary
On Thu, Jul 12, 2012 at 8:40 AM, Aaron Collier<[email protected]>
wrote:
Firefox is the leader on our stats, but I think that's mostly because it
is the default browser on almost any campus system. IE is close behind
though while mobile browsers are the most sparse.
I guess the old "develop in firefox, test in IE" still holds true.
Aaron Collier
Library Academic Systems Analyst
California State University, Fresno - Henry Madden Library
559.278.2945
[email protected]
http://www.csufresno.edu/library
----- Original Message -----
From: "Brig C McCoy"<[email protected]>
To: [email protected]
Sent: Thursday, July 12, 2012 8:28:03 AM
Subject: Re: [CODE4LIB] Browser Wars
Hi...
This is from the last six weeks from one of my public-facing websites.
Definitely not going to drop MSIE support for the website at this rate:
# #reqs #pages browser
1 18137 827 MSIE
8651 437 MSIE/8
7400 277 MSIE/9
1866 52 MSIE/7
193 42 MSIE/6
16 16 MSIE/5
11 3 MSIE/10
2 1809 441 Safari
1128 299 Safari/533
202 58 Safari/534
214 54 Safari/7534
79 23 Safari/6533
41 4 Safari/530
13 3 Safari/531
3 906 260 Netscape (compatible)
4 1287 182 Firefox
442 114 Firefox/13
408 34 Firefox/12
139 11 Firefox/10
163 6 Firefox/3
28 6 Firefox/14
11 5 Firefox/9
6 2 Firefox/4
12 2 Firefox/6
4 1 Firefox/15
8 1 Firefox/7
5 1164 175 Chrome
718 111 Chrome/19
409 61 Chrome/20
23 1 Chrome/9
4 1 Chrome/10
1 1 Chrome/5
...brig
On 7/12/2012 9:33 AM, Michael Schofield wrote:
Ever since Microsoft announced the new IE auto-update policy, the
blogosphere is fussing. This is definitely important (and good) news,
but sites-Smashing Magazine has three articles on it in the last few
days-are really pushing the "drop IE support," and "its literally
slowing the internet down." I'm down, but that attitude-especially
for libraries-isn't really the right one to have. It is, IMHO, an old
view. A smart design strategy with progressive enhancement can
deliver content to . everyone - which should be the priority for
non-prof / [local-]government web presences over flare. Right?--
Brig C. McCoy [email protected]
Network Services Coordinator
Kansas City, Kansas Public Library
625 Minnesota Avenue
Kansas City, KS 66101
tel 913-279-2349
cel 816-885-2700
fax 913-279-2271
--
Cary Gordon
The Cherry Hill Company
http://chillco.com
--
Shaun D. Ellis
Digital Library Interface Developer
Firestone Library, Princeton University
voice: 609.258.1698 | [email protected]
