Re: Dealing with IE6
- From: Andy Dingley <dingbat@xxxxxxxxxxxxxx>
- Date: Tue, 9 Jun 2009 05:05:27 -0700 (PDT)
On 9 June, 08:11, "Nik Coughlin" <nrkn....@xxxxxxxxx> wrote:
Further to my critique request, and out of a wish to mollify as many
naysayers as possible, rather than the "arrogant" technique of informing
users that a site looks bad because they're using an old browser, what would
you say would be the best course of action?
Your "IE6 sucks" message is fine. IE6 _does_ suck. There are also
rational upgrade paths away from it, for pretty much all users.
Caveats:
* Don't make the message excessive.
* Make the messsage disappear over time. Client-side JavaScript / week-
long cookie will show it once per week for that user and that's
plenty. This is also a good example of something where graceful
fallback for non-JS users is entirely aceptable. If they're still
using IE6, they might have a good reason that they have to. Don't rub
their noses in it.
* Maintain the message. Don't put up any messages that will begin to
look ridiculous in less than the site's lifetime. Saying "Your IE6 is
old" is OK, suggesting an "Upgrade to IE7" already looks dated and so
will "Upgrade to IE8" or IE9 within a few years, when IE11 is around
and renamed "Encarta 11"
* Make the message accurate. Don't serve "Your IE is old, upgrade to a
newer IE" message _unless_ you're certain that they're not a Unix
user. Or else they're running BSD, in which case they see it as a form
of flattery and their superiority over the feeble Windows lusers.
Certainly don't trust browser-sniff strings.
.
- Follow-Ups:
- Re: Dealing with IE6
- From: dorayme
- Re: Dealing with IE6
- References:
- Dealing with IE6
- From: Nik Coughlin
- Dealing with IE6
- Prev by Date: Re: Change content based on web host
- Next by Date: Re: CSS question - inheriting other classes (I think)
- Previous by thread: Re: Dealing with IE6
- Next by thread: Re: Dealing with IE6
- Index(es):
Relevant Pages
|
