<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: feature-testing</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/feature-testing.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2008-12-22T10:58:45+00:00</updated><author><name>Simon Willison</name></author><entry><title>jQuery changeset 5985</title><link href="https://simonwillison.net/2008/Dec/22/jquery/#atom-tag" rel="alternate"/><published>2008-12-22T10:58:45+00:00</published><updated>2008-12-22T10:58:45+00:00</updated><id>https://simonwillison.net/2008/Dec/22/jquery/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://dev.jquery.com/changeset/5985"&gt;jQuery changeset 5985&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
jQuery trunk has ditched browser sniffing in favour of feature testing, where a small suite of unit-test-like code blocks is used to detect whether a browser supports specific idioms. If the tests fail jQuery still makes assumptions about what the fix is, but it’s not hard to imagine the library eventually using code tests to ensure the fix will work as well.

    &lt;p&gt;&lt;small&gt;&lt;/small&gt;Via &lt;a href="http://blog.clintecker.com/post/66129101/as-of-5985-jquery-advocates-feature-detection-over"&gt;Clint Ecker&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/feature-testing"&gt;feature-testing&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/javascript"&gt;javascript&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/jquery"&gt;jquery&lt;/a&gt;&lt;/p&gt;



</summary><category term="feature-testing"/><category term="javascript"/><category term="jquery"/></entry></feed>