jQuery Forum

Hey there, John.<div>
</div><div>It seems that 1.3 doesn't allow attribute selectors to have any spaces.</div><div>
</div><div>$("a[ name ]") is 1.2.6 selected all anchors with a name attribute. 1.3 throws "Syntax error, unrecognized expression: [ name ]".</div>
<div>
</div><div>Removing the space and it works in 1.3.</div><div>$("a[name]");</div><div>
</div><div>Is this intended?</div><div><div>_____________________________________
Brad Brizendine
CTO, Glyphix <a href="http://www.glyphix.com/">http://www.glyphix.com/</a>

everything's working for me now, as of RC2.
i'll get busy porting my whole webapp to v1.3, but if you want any
kind of decent bug reports, it would be nice to know where and how to
use all the new functionality introduced, any place to see an updated
API doc before final release? otherwise all u'll get are regression
bugs from me : ) i have A LOT of stuff waiting to be ported to $.live,
away from $.listen and $.bubble, but i have no idea how to use it or
to make equivalent triggers similar to bubble.
thx,
Leon

> jQuery 1.3rc2 is ready.
It certainly is! It's rockin' for me - all my plugins are running w/o
a hitch. Great work, everybody!

Hmm... it might have to make it in to the release but I'll tweak it
later. Could you file a quick bug on it?
http://dev.jquery.com/
Thanks!
--John

Another one: <a href="http://jquery.glyphix.com/1.3/">http://jquery.glyphix.com/1.3/</a><div>
</div><div>In ie7, I get:</div><div><ul><li>Line 2159: "object doesn't support this property or method"
</li>
<li>Line 29: "object doesn't support this property or method"</li></ul><div>Everything's working great in FF (as long as there are no spaces in attribute selectors).</div><div>
</div><div>I updated my test page to include both issues: <a href="http://jquery.glyphix.com/1.3/">http://jquery.glyphix.com/1.3/</a></div>
<div>
</div>_____________________________________
Brad Brizendine
CTO, Glyphix <a href="http://www.glyphix.com/">http://www.glyphix.com/</a>

Sure thing: <a href="http://dev.jquery.com/ticket/3831">http://dev.jquery.com/ticket/3831</a><div>
</div><div>Glad to be able to contribute.<br clear="all">_____________________________________
Brad Brizendine
CTO, Glyphix <a href="http://www.glyphix.com/">http://www.glyphix.com/</a>

> Another one: http://jquery.glyphix.com/1.3/

jQuery UI 1.6rc4 isn't working properly with jQuery 1.3rc2 in Safari 3
& Firefox 3 (haven't tested IE). I'm not sure whether it's 1.3's
fault, or whether UI just needs to be updated for it. I have an
example page here:
    http://danielbergey.com/jquery/jquery_droppable_bug_broken_using_13rc2.html
    http://danielbergey.com/jquery/jquery_droppable_bug_works_using_13b1.html
This test works with jQuery 1.3b1, and fails with 1.3b2, rc1, and rc2.
Daniel Bergey
(Emailed this to you directly as well, not sure which was better/
faster.)

if anyone has stumbled upon a link to the new v1.3 API doc, s/he will
be rewarded with royalty-free bug reports...

AFAIK there is no docs yet, but I learned a lot from the sourcecode, as aways.
One featured that I'm already using is the event delegation functions. They are similar to the functionality provided by the widely known livequery plugin.
jQuery.live(type, fn) is ment to be similar to jQuery.livequery(type,fn)
jQuery.die(type,fn) is ment to be similar to jQuery.expire(live,fn)
But jQuery 1.3 provides this in a much better and performative way, thanks to John! =)
If some of you wish to understand a little about how it works you can look into livequery documentation [ <a href="http://docs.jquery.com/Plugins/livequery">http://docs.jquery.com/Plugins/livequery</a> ]. But be aware that not all livequery features are covered by 1.3, just the ones mentioned above.
Also, don't forget to look into the previous beta anouncements and at jQuery blog. Some info can be found there.

i dont see how it can work like livequery, since all livequery seems
to do is bind on a timer. delegation requires binding to a parent
container and filtering out events/element targets.
something like Ariel's $.listen was $("#container").listen("click",
"p, span", function(e){alert("callback")});
the only way to delegate without specifying a container would probably
be to implicitly bind any event handlers to <html> or <body>, is that
what happens in $.live?
Leon

> the only way to delegate without specifying a container would probably

Nice! :)
Now I'm just waiting patiently for the updated Validation plugin. :)

> i dont see how it can work like livequery
I ment how you use it, not how it functions internaly. Both of them receive 2 params, eventType and callbackFunction. I just wanted to point out that anyone familiar with $(sel).livequery(type,fn) shoud be confortable with $(sel).live(type,fn).
Sorry for the confusion.
<br clear="all">--
Iraê

I've fixed both of these issues.
Attributes spacing:
http://github.com/jeresig/sizzle/commit/edac9ac5eab8f5ff61f68315a7638c55205f5682
XML Errors in IE:
http://github.com/jeresig/sizzle/commit/010bb7c6c508ef56118c0d06c90cc82fb831ad6b
Should be merged into jQuery core momentarily.
--John

Yes! Thanks, John.<br clear="all">_____________________________________
Brad Brizendine
CTO, Glyphix <a href="http://www.glyphix.com/">http://www.glyphix.com/</a>

John,
On a page in a webapp I'm working on I get a infinite* loop at line
1769:
for ( var i = 0; !curLoop[i]; i++ ){}
in Firefox 3. WebKit does not have the same error.
Same page worked fine in 1.2.6 and in 1.3b2. I'll try to get a
reduction/testcase later on tonight (working under a deadline right
now), but thought I'd give the heads up that I ran into that.
D
* FF aborts around i = 114318046, I assume it's infinite :)

Sorry, I take that back -- the loop occurs in 1.3b2 as well, it must
be a change made locally within the past several hours. I'll update if
I sort it out.
D

Does this release address the cleartype issue in IE internally or do
we still need to work around this in our code ?
Thanks,
Dave Buchholz