<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <id>http://groups.google.com/group/jquery-dev</id>
  <title type="text">jQuery Development Google Group</title>
  <subtitle type="text">
  The future and development issues of jQuery, a wonderful Javascript library.
  </subtitle>
  <link href="/group/jquery-dev/feed/atom_v1_0_msgs.xml" rel="self" title="jQuery Development feed"/>
  <updated>2010-01-04T20:04:01Z</updated>
  <generator uri="http://groups.google.com" version="1.99">Google Groups</generator>
  <entry>
  <author>
  <name>ajpiano</name>
  <email>ajpi...@gmail.com</email>
  </author>
  <updated>2010-01-04T20:04:01Z</updated>
  <id>http://groups.google.com/group/jquery-dev/browse_frm/thread/1ec8bf1f2a8015ec/483d09072513e06e?show_docid=483d09072513e06e</id>
  <link href="http://groups.google.com/group/jquery-dev/browse_frm/thread/1ec8bf1f2a8015ec/483d09072513e06e?show_docid=483d09072513e06e"/>
  <title type="text">Re: Any thought on Event filter?</title>
  <summary type="html" xml:space="preserve">
  This strikes me as almost a little bit too much sugar...to streamline &lt;br&gt; this type of binding/filtering, I tend to think it might just be &lt;br&gt; easier to perhaps use the jQuery.ui.keyCode object and move that into &lt;br&gt; core, perhaps? I think the idea is to save people needing to do the &lt;br&gt; keycode lookups, not necessarily complicate the event binding syntax.
  </summary>
  </entry>
  <entry>
  <author>
  <name>Mike Taylor</name>
  <email>miketa...@gmail.com</email>
  </author>
  <updated>2010-01-04T19:46:41Z</updated>
  <id>http://groups.google.com/group/jquery-dev/browse_frm/thread/e12cabd79b717b6a/a60c406e3e362c2b?show_docid=a60c406e3e362c2b</id>
  <link href="http://groups.google.com/group/jquery-dev/browse_frm/thread/e12cabd79b717b6a/a60c406e3e362c2b?show_docid=a60c406e3e362c2b"/>
  <title type="text">Re: [jquery-dev] nightly</title>
  <summary type="html" xml:space="preserve">
  Ah, yes. My bad. I didn&#39;t realize (or had forgotten?) that everything on &lt;br&gt; jquery.com was on a CDN.
  </summary>
  </entry>
  <entry>
  <author>
  <name>John Resig</name>
  <email>jere...@gmail.com</email>
  </author>
  <updated>2010-01-04T19:44:03Z</updated>
  <id>http://groups.google.com/group/jquery-dev/browse_frm/thread/e12cabd79b717b6a/25fd1b5f1837da3b?show_docid=25fd1b5f1837da3b</id>
  <link href="http://groups.google.com/group/jquery-dev/browse_frm/thread/e12cabd79b717b6a/25fd1b5f1837da3b?show_docid=25fd1b5f1837da3b"/>
  <title type="text">Re: [jquery-dev] nightly</title>
  <summary type="html" xml:space="preserve">
  As I&#39;ve mentioned before, the problem isn&#39;t generating the file - it&#39;s &lt;br&gt; the fact that the CDN caches everything out the wazoo and it&#39;s really &lt;br&gt; hard to force all the leaf nodes to update in an automated fashion. &lt;br&gt; Once we figure that out we&#39;ll be able to do nightlies in a more-timely &lt;br&gt; fashion. &lt;br&gt; --John
  </summary>
  </entry>
  <entry>
  <author>
  <name>Mike Taylor</name>
  <email>miketa...@gmail.com</email>
  </author>
  <updated>2010-01-04T19:09:36Z</updated>
  <id>http://groups.google.com/group/jquery-dev/browse_frm/thread/e12cabd79b717b6a/8a0a5c1758670c03?show_docid=8a0a5c1758670c03</id>
  <link href="http://groups.google.com/group/jquery-dev/browse_frm/thread/e12cabd79b717b6a/8a0a5c1758670c03?show_docid=8a0a5c1758670c03"/>
  <title type="text">nightly</title>
  <summary type="html" xml:space="preserve">
  As a number of people have mentioned in a previous thread (http:// &lt;br&gt; groups.google.com/group/jquery -dev/browse_thread/thread/ &lt;br&gt; 94cd4ab2543d3b01/a62a699a01d4f 425?lnk=gst&amp;amp;q=nightly&amp;amp;pli=1), and &lt;br&gt; elsewhere in #jquery on freenode-- the nightly at &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://code.jquery.com/nightlies/jquery-nightly.js&quot;&gt;[link]&lt;/a&gt; isn&#39;t quite nightly
  </summary>
  </entry>
  <entry>
  <author>
  <name>DBJDBJ</name>
  <email>dbj...@gmail.com</email>
  </author>
  <updated>2010-01-04T18:48:05Z</updated>
  <id>http://groups.google.com/group/jquery-dev/browse_frm/thread/b2be650018ab490b/88fb561b8034ca4b?show_docid=88fb561b8034ca4b</id>
  <link href="http://groups.google.com/group/jquery-dev/browse_frm/thread/b2be650018ab490b/88fb561b8034ca4b?show_docid=88fb561b8034ca4b"/>
  <title type="text">Re: jQuery.fragments and simple HTML</title>
  <summary type="html" xml:space="preserve">
  &amp;quot;Confusion is always the most honest response.&amp;quot; &lt;br&gt; -- Marty Indik
  </summary>
  </entry>
  <entry>
  <author>
  <name>James Padolsey</name>
  <email>jamespadol...@googlemail.com</email>
  </author>
  <updated>2010-01-04T14:14:31Z</updated>
  <id>http://groups.google.com/group/jquery-dev/browse_frm/thread/b2be650018ab490b/862d11b5f1fd81ab?show_docid=862d11b5f1fd81ab</id>
  <link href="http://groups.google.com/group/jquery-dev/browse_frm/thread/b2be650018ab490b/862d11b5f1fd81ab?show_docid=862d11b5f1fd81ab"/>
  <title type="text">Re: jQuery.fragments and simple HTML</title>
  <summary type="html" xml:space="preserve">
  Hmmm, running those tests again, it seems that there is only a slight &lt;br&gt; difference (and very inconsistent). Before, I didn&#39;t consider the &lt;br&gt; effects of resolving the global &amp;quot;document&amp;quot; in &lt;br&gt; &amp;quot;document.createElement&amp;quot;... &lt;br&gt; A really primitive test: &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://jsbin.com/irubu&quot;&gt;[link]&lt;/a&gt; &lt;br&gt; Anyway, I&#39;m glad to hear that a templating solution is being
  </summary>
  </entry>
  <entry>
  <author>
  <name>John Resig</name>
  <email>jere...@gmail.com</email>
  </author>
  <updated>2010-01-04T13:24:13Z</updated>
  <id>http://groups.google.com/group/jquery-dev/browse_frm/thread/b2be650018ab490b/9b208c30fc047f78?show_docid=9b208c30fc047f78</id>
  <link href="http://groups.google.com/group/jquery-dev/browse_frm/thread/b2be650018ab490b/9b208c30fc047f78?show_docid=9b208c30fc047f78"/>
  <title type="text">Re: [jquery-dev] jQuery.fragments and simple HTML</title>
  <summary type="html" xml:space="preserve">
  I would definitely need to see proof of cloneNode being faster than &lt;br&gt; createElement before moving forward with something like this &lt;br&gt; (especially in IE). &lt;br&gt; Although, I&#39;m a bit hesitant landing a change like this, wholesale - &lt;br&gt; mostly because we&#39;re looking at better templating solutions for after &lt;br&gt; 1.4 and this seems hacky, at best.
  </summary>
  </entry>
  <entry>
  <author>
  <name>James Padolsey</name>
  <email>jamespadol...@googlemail.com</email>
  </author>
  <updated>2010-01-04T12:50:37Z</updated>
  <id>http://groups.google.com/group/jquery-dev/browse_frm/thread/b2be650018ab490b/84443f31337d450a?show_docid=84443f31337d450a</id>
  <link href="http://groups.google.com/group/jquery-dev/browse_frm/thread/b2be650018ab490b/84443f31337d450a?show_docid=84443f31337d450a"/>
  <title type="text">jQuery.fragments and simple HTML</title>
  <summary type="html" xml:space="preserve">
  I&#39;ve been looking into jQuery.fragments and have a couple of &lt;br&gt; suggestions. &lt;br&gt; It&#39;d be useful, I think, if jQuery.fragments could be used to store &lt;br&gt; basic DOM nodes as well, for example (currently it only stores &lt;br&gt; fragments): &lt;br&gt; jQuery.fragments[&#39;&amp;lt;div/&amp;gt;&#39;] = document.createElement(&#39;div&#39;); &lt;br&gt; ... &lt;br&gt; cachedDiv.cloneNode(false); seems to be faster than
  </summary>
  </entry>
  <entry>
  <author>
  <name>Michael</name>
  <email>md.drey...@gmail.com</email>
  </author>
  <updated>2010-01-03T20:30:16Z</updated>
  <id>http://groups.google.com/group/jquery-dev/browse_frm/thread/25e9ebc58184a277/4f967893f7873b82?show_docid=4f967893f7873b82</id>
  <link href="http://groups.google.com/group/jquery-dev/browse_frm/thread/25e9ebc58184a277/4f967893f7873b82?show_docid=4f967893f7873b82"/>
  <title type="text">Tablesorter digit problem with Heroku</title>
  <summary type="html" xml:space="preserve">
  I&#39;ve tried two methods for having the tablesorter plugin &lt;br&gt; (tablesorter.com) sort as digits: &lt;br&gt; 1) Inline: &lt;br&gt; &amp;lt;table id=&amp;quot;teams_table&amp;quot; class=&amp;quot;tablesorter {sorter: &#39;digit&#39;}&amp;quot; &lt;br&gt; border=&amp;quot;1&amp;quot; rules=&amp;quot;all&amp;quot; frame=&amp;quot;box&amp;quot; cellpadding=&amp;quot;2&amp;quot;&amp;gt; &lt;br&gt; 2) In my jquery file: &lt;br&gt; $(&amp;quot;#teams_table&amp;quot;).tablesorter( { &lt;br&gt; sortList: [[3,1],[6,1],[4,1],[9,1],[7,1] ],
  </summary>
  </entry>
  <entry>
  <author>
  <name>Karel Minarik</name>
  <email>karel.mina...@gmail.com</email>
  </author>
  <updated>2010-01-03T23:07:48Z</updated>
  <id>http://groups.google.com/group/jquery-dev/browse_frm/thread/13b78bd9e2c78c90/57b464d68b7c1852?show_docid=57b464d68b7c1852</id>
  <link href="http://groups.google.com/group/jquery-dev/browse_frm/thread/13b78bd9e2c78c90/57b464d68b7c1852?show_docid=57b464d68b7c1852"/>
  <title type="text">Re: Problems with QUnit async tests</title>
  <summary type="html" xml:space="preserve">
  That&#39;d be too good :) But no, this &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://pastie.textmate.org/765397&quot;&gt;[link]&lt;/a&gt; &lt;br&gt; is the full test suite. When the Firebug panel is active *and* open, &lt;br&gt; it runs through all cases. When the panel is closed (with Firebug &lt;br&gt; active), I am getting only partial results (cca half of the cases is &lt;br&gt; run)... Really weird. &lt;br&gt; Karel
  </summary>
  </entry>
  <entry>
  <author>
  <name>John Resig</name>
  <email>jere...@gmail.com</email>
  </author>
  <updated>2010-01-03T21:04:11Z</updated>
  <id>http://groups.google.com/group/jquery-dev/browse_frm/thread/13b78bd9e2c78c90/cc6356ef66cbf421?show_docid=cc6356ef66cbf421</id>
  <link href="http://groups.google.com/group/jquery-dev/browse_frm/thread/13b78bd9e2c78c90/cc6356ef66cbf421?show_docid=cc6356ef66cbf421"/>
  <title type="text">Re: [jquery-dev] Re: Problems with QUnit async tests</title>
  <summary type="html" xml:space="preserve">
  I take it that you left some console.log() statements in your code and &lt;br&gt; they&#39;re breaking since you don&#39;t have Firebug open. &lt;br&gt; --John
  </summary>
  </entry>
  <entry>
  <author>
  <name>Karel Minarik</name>
  <email>karel.mina...@gmail.com</email>
  </author>
  <updated>2010-01-03T20:57:58Z</updated>
  <id>http://groups.google.com/group/jquery-dev/browse_frm/thread/13b78bd9e2c78c90/da90bed24a732119?show_docid=da90bed24a732119</id>
  <link href="http://groups.google.com/group/jquery-dev/browse_frm/thread/13b78bd9e2c78c90/da90bed24a732119?show_docid=da90bed24a732119"/>
  <title type="text">Re: Problems with QUnit async tests</title>
  <summary type="html" xml:space="preserve">
  Just noticed a really strange behaviour: all the tests run in Firefox &lt;br&gt; when and only when I have Firebug panel open. With Firebug closed/ &lt;br&gt; suspended, different of tests run on each page load and it never &lt;br&gt; finishes. Any idea why this is happening? &lt;br&gt; Karel
  </summary>
  </entry>
  <entry>
  <author>
  <name>Karel Minarik</name>
  <email>karel.mina...@gmail.com</email>
  </author>
  <updated>2010-01-03T20:41:27Z</updated>
  <id>http://groups.google.com/group/jquery-dev/browse_frm/thread/13b78bd9e2c78c90/3210a959c7fbc097?show_docid=3210a959c7fbc097</id>
  <link href="http://groups.google.com/group/jquery-dev/browse_frm/thread/13b78bd9e2c78c90/3210a959c7fbc097?show_docid=3210a959c7fbc097"/>
  <title type="text">Re: Problems with QUnit async tests</title>
  <summary type="html" xml:space="preserve">
  Hello John, &lt;br&gt; thank you very much for the clarification. If I stick with the &amp;quot;one &lt;br&gt; assertion per async test&amp;quot; everything works really fine. (Though only &lt;br&gt; in FF, Safari gives some couch related issues -- no_db_file in setup, &lt;br&gt; has still trouble going through the entire suite, etc. Also, Celerity &lt;br&gt; does not show the results, while it has been working for a limited
  </summary>
  </entry>
  <entry>
  <author>
  <name>Rick Waldron</name>
  <email>waldron.r...@gmail.com</email>
  </author>
  <updated>2010-01-03T18:13:51Z</updated>
  <id>http://groups.google.com/group/jquery-dev/browse_frm/thread/6efc327d93bc0ad0/6363be97e438d20c?show_docid=6363be97e438d20c</id>
  <link href="http://groups.google.com/group/jquery-dev/browse_frm/thread/6efc327d93bc0ad0/6363be97e438d20c?show_docid=6363be97e438d20c"/>
  <title type="text">Re: [jquery-dev] Web Sockets</title>
  <summary type="html" xml:space="preserve">
  Agreed... I&#39;ve been having some fun with this. At some point I&#39;d like to clean up my test stuff and publish it... Will post when ready &lt;br&gt; Rick &lt;br&gt; -- Sent from my Palm Prē &lt;br&gt; very nice work, thanks.-- &lt;br&gt; Hüseyin Mert &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://www.hmert.com&quot;&gt;[link]&lt;/a&gt; &lt;br&gt; Hello. &lt;br&gt; Web Sockets someone try? &lt;br&gt; Web Sockets Now Available In Google Chrome.
  </summary>
  </entry>
  <entry>
  <author>
  <name>John Resig</name>
  <email>jere...@gmail.com</email>
  </author>
  <updated>2010-01-03T18:00:31Z</updated>
  <id>http://groups.google.com/group/jquery-dev/browse_frm/thread/13b78bd9e2c78c90/2c0a3b0cb425b07b?show_docid=2c0a3b0cb425b07b</id>
  <link href="http://groups.google.com/group/jquery-dev/browse_frm/thread/13b78bd9e2c78c90/2c0a3b0cb425b07b?show_docid=2c0a3b0cb425b07b"/>
  <title type="text">Re: [jquery-dev] Problems with QUnit async tests</title>
  <summary type="html" xml:space="preserve">
  The stop() method doesn&#39;t really work that way (it would have to &lt;br&gt; behave synchronously for that to be the case). You&#39;ll have to do one &lt;br&gt; stop() at the start of the test block and then either do only one &lt;br&gt; async test or just keep a counter of the number of tests that&#39;ve &lt;br&gt; completed and only run the start() after all of them have returned.
  </summary>
  </entry>
</feed>
