jQuery Development Google Group

Re: Any thought on Event filter?

ajpi...@gmail.com (ajpiano) — Mon, 04 Jan 2010 20:04:01 UT

This strikes me as almost a little bit too much sugar...to streamline
this type of binding/filtering, I tend to think it might just be
easier to perhaps use the jQuery.ui.keyCode object and move that into
core, perhaps? I think the idea is to save people needing to do the
keycode lookups, not necessarily complicate the event binding syntax.

Re: [jquery-dev] nightly

miketa...@gmail.com (Mike Taylor) — Mon, 04 Jan 2010 19:46:41 UT

Ah, yes. My bad. I didn't realize (or had forgotten?) that everything on
jquery.com was on a CDN.

Re: [jquery-dev] nightly

jere...@gmail.com (John Resig) — Mon, 04 Jan 2010 19:44:03 UT

As I've mentioned before, the problem isn't generating the file - it's
the fact that the CDN caches everything out the wazoo and it's really
hard to force all the leaf nodes to update in an automated fashion.
Once we figure that out we'll be able to do nightlies in a more-timely
fashion.
--John

nightly

miketa...@gmail.com (Mike Taylor) — Mon, 04 Jan 2010 19:09:36 UT

As a number of people have mentioned in a previous thread (http://
groups.google.com/group/jquery -dev/browse_thread/thread/
94cd4ab2543d3b01/a62a699a01d4f 425?lnk=gst&q=nightly&pli=1), and
elsewhere in #jquery on freenode-- the nightly at
[link] isn't quite nightly

Re: jQuery.fragments and simple HTML

dbj...@gmail.com (DBJDBJ) — Mon, 04 Jan 2010 18:48:05 UT

"Confusion is always the most honest response."
-- Marty Indik

Re: jQuery.fragments and simple HTML

jamespadol...@googlemail.com (James Padolsey) — Mon, 04 Jan 2010 14:14:31 UT

Hmmm, running those tests again, it seems that there is only a slight
difference (and very inconsistent). Before, I didn't consider the
effects of resolving the global "document" in
"document.createElement"...
A really primitive test: [link]
Anyway, I'm glad to hear that a templating solution is being

Re: [jquery-dev] jQuery.fragments and simple HTML

jere...@gmail.com (John Resig) — Mon, 04 Jan 2010 13:24:13 UT

I would definitely need to see proof of cloneNode being faster than
createElement before moving forward with something like this
(especially in IE).
Although, I'm a bit hesitant landing a change like this, wholesale -
mostly because we're looking at better templating solutions for after
1.4 and this seems hacky, at best.

jQuery.fragments and simple HTML

jamespadol...@googlemail.com (James Padolsey) — Mon, 04 Jan 2010 12:50:37 UT

I've been looking into jQuery.fragments and have a couple of
suggestions.
It'd be useful, I think, if jQuery.fragments could be used to store
basic DOM nodes as well, for example (currently it only stores
fragments):
jQuery.fragments['<div/>'] = document.createElement('div');
...
cachedDiv.cloneNode(false); seems to be faster than

Tablesorter digit problem with Heroku

md.drey...@gmail.com (Michael) — Sun, 03 Jan 2010 20:30:16 UT

I've tried two methods for having the tablesorter plugin
(tablesorter.com) sort as digits:
1) Inline:
<table id="teams_table" class="tablesorter {sorter: 'digit'}"
border="1" rules="all" frame="box" cellpadding="2">
2) In my jquery file:
$("#teams_table").tablesorter( {
sortList: [[3,1],[6,1],[4,1],[9,1],[7,1] ],

Re: Problems with QUnit async tests

karel.mina...@gmail.com (Karel Minarik) — Sun, 03 Jan 2010 23:07:48 UT

That'd be too good :) But no, this [link]
is the full test suite. When the Firebug panel is active *and* open,
it runs through all cases. When the panel is closed (with Firebug
active), I am getting only partial results (cca half of the cases is
run)... Really weird.
Karel

Re: [jquery-dev] Re: Problems with QUnit async tests

jere...@gmail.com (John Resig) — Sun, 03 Jan 2010 21:04:11 UT

I take it that you left some console.log() statements in your code and
they're breaking since you don't have Firebug open.
--John

Re: Problems with QUnit async tests

karel.mina...@gmail.com (Karel Minarik) — Sun, 03 Jan 2010 20:57:58 UT

Just noticed a really strange behaviour: all the tests run in Firefox
when and only when I have Firebug panel open. With Firebug closed/
suspended, different of tests run on each page load and it never
finishes. Any idea why this is happening?
Karel

Re: Problems with QUnit async tests

karel.mina...@gmail.com (Karel Minarik) — Sun, 03 Jan 2010 20:41:27 UT

Hello John,
thank you very much for the clarification. If I stick with the "one
assertion per async test" everything works really fine. (Though only
in FF, Safari gives some couch related issues -- no_db_file in setup,
has still trouble going through the entire suite, etc. Also, Celerity
does not show the results, while it has been working for a limited

Re: [jquery-dev] Web Sockets

waldron.r...@gmail.com (Rick Waldron) — Sun, 03 Jan 2010 18:13:51 UT

Agreed... I've been having some fun with this. At some point I'd like to clean up my test stuff and publish it... Will post when ready
Rick
-- Sent from my Palm Prē
very nice work, thanks.--
Hüseyin Mert
[link]
Hello.
Web Sockets someone try?
Web Sockets Now Available In Google Chrome.

Re: [jquery-dev] Problems with QUnit async tests

jere...@gmail.com (John Resig) — Sun, 03 Jan 2010 18:00:31 UT

The stop() method doesn't really work that way (it would have to
behave synchronously for that to be the case). You'll have to do one
stop() at the start of the test block and then either do only one
async test or just keep a counter of the number of tests that've
completed and only run the start() after all of them have returned.