Received: by 10.224.113.75 with SMTP id z11mr118596qap.15.1307136291033;
        Fri, 03 Jun 2011 14:24:51 -0700 (PDT)
X-BeenThere: d3-js@googlegroups.com
Received: by 10.224.187.71 with SMTP id cv7ls600472qab.1.gmail; Fri, 03 Jun
 2011 14:24:50 -0700 (PDT)
Received: by 10.224.192.193 with SMTP id dr1mr107256qab.9.1307136290688;
        Fri, 03 Jun 2011 14:24:50 -0700 (PDT)
Received: by 10.224.192.193 with SMTP id dr1mr107255qab.9.1307136290668;
        Fri, 03 Jun 2011 14:24:50 -0700 (PDT)
Return-Path: <nelson.mi...@gmail.com>
Received: from mail-vw0-f45.google.com (mail-vw0-f45.google.com [209.85.212.45])
        by gmr-mx.google.com with ESMTPS id k32si1942578qcs.1.2011.06.03.14.24.49
        (version=TLSv1/SSLv3 cipher=OTHER);
        Fri, 03 Jun 2011 14:24:49 -0700 (PDT)
Received-SPF: pass (google.com: domain of nelson.mi...@gmail.com designates 209.85.212.45 as permitted sender) client-ip=209.85.212.45;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of nelson.mi...@gmail.com designates 209.85.212.45 as permitted sender) smtp.mail=nelson.mi...@gmail.com; dkim=pass (test mode) header...@gmail.com
Received: by vws17 with SMTP id 17so1898336vws.4
        for <d3-js@googlegroups.com>; Fri, 03 Jun 2011 14:24:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:sender:date:x-google-sender-auth
         :message-id:subject:from:to:content-type;
        bh=IPKUR1y63ufu+6ZVaoFdUe6BNMjZZK0Ta8O2La01jRg=;
        b=EMPrMJTeZkxlzfjgk5NY4awU2f1RjwdXaJV3jVBGhyuO0vg/ynsVAPbcw+H12QUbuA
         6HDESOIIDcbWqIwvCM5NJFdO32mdyFbwnTWoe1W2HBoZGWyjdhFWYel8GG7rXmAF5jcd
         BrXRUwCgZfJdBMhbty0sH3kyWWbrake1dmYH8=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:date:x-google-sender-auth:message-id:subject
         :from:to:content-type;
        b=CWJO/r21US1cMVk5e7u8cyOfAudrFiamT0WmQGvvtDO14+hWqEu4hzHELnolLIOPKa
         uh5kbikcuJaqrwn4H70adWD2jzMTwQBarthM8/U7XHWABs+KfBo6XKESkarxYYFATy49
         /UFq1NjiduSxRpADv2fw0opOngPfmQDXaNBtg=
MIME-Version: 1.0
Received: by 10.220.199.73 with SMTP id er9mr800632vcb.83.1307136289308; Fri,
 03 Jun 2011 14:24:49 -0700 (PDT)
Sender: nelson.mi...@gmail.com
Received: by 10.220.192.204 with HTTP; Fri, 3 Jun 2011 14:24:49 -0700 (PDT)
Date: Fri, 3 Jun 2011 14:24:49 -0700
Message-ID: <BANLkTik6kxmNZ=yrTbnvDt6vum=ndEd...@mail.gmail.com>
Subject: best way to catch browsers without SVG?
From: Nelson Minar <nel...@monkey.org>
To: d3-js@googlegroups.com
Content-Type: multipart/alternative; boundary=90e6ba53b070327fa204a4d56292

--90e6ba53b070327fa204a4d56292
Content-Type: text/plain; charset=UTF-8

I'm about to launch a data visualization site that uses D3 and Polymaps and,
consequently, a whole lot of SVG. What's the recommended way to catch users
who don't have SVG support in their browsers and give them something to look
at? All I need is a redirect or a link to a page saying "get a new browser".

It'd probably get 95% of the folks if I just sniff the browser and see if
they're running IE 6, 7, or 8.  But it'd be cooler to have some automatic
fallback or feature detection.

--90e6ba53b070327fa204a4d56292
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I&#39;m about to launch a data visualization site that uses D3 and Polymaps=
 and, consequently, a whole lot of SVG. What&#39;s the recommended way to c=
atch users who don&#39;t have SVG support in their browsers and give them s=
omething to look at? All I need is a redirect or a link to a page saying &q=
uot;get a new browser&quot;.<div>
<br></div><div>It&#39;d probably get 95% of the folks if I just sniff the b=
rowser and see if they&#39;re running IE 6, 7, or 8. =C2=A0But it&#39;d be =
cooler to have some automatic fallback or feature detection.</div><div><br>=
</div>

--90e6ba53b070327fa204a4d56292--