1.3b2 trouble with selectors on nested contexts in XML documents
Hi, guys. So far, 1.3b2 is a drop-in replacement for my most recent work. I've run into only one issue so far. I documented it here: http://jquery.glyphix.com/1.3/ I'm happy to make a ticket for it, but I'm not sure if it's been reported yet.
jQuery 1.3 beta 2 - :not selector still has problems
<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Hi John, et. al.,</div>It looks like the :not filter been fixed with regard to the selector expression $('li:not(:odd)'), but it still is throwing an error with $('li:not(:last-child)') : <div><span class="Apple-tab-span" style="white-space:pre"> </span>match[3] is undefined (line 1862)</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>match[3] = match[3].match(chunker).length
offset bug for fixed elements (chrome/safari)
Bug ticket: http://dev.jquery.com/ticket/3341 Found in jQuery 1.3 Beta 2 Offset of the fixed element doesn't include document scroll. In my test case it was caused by the parent table. If there are no parents, then offset is correct.
1.3 .live performance
Hi Is there any performance degradation in using .live rather than .bind in 1.3? Does it use a timer internally ? cheers Jonah
.live() delegation fails in second handler if first handler modify the DOM
I'm using 1.3b2 (6070) and found the following behavior. - using 2 .live() handlers for same link. - 1st handler always fire and modify the link with .html(string) - 2nd handler fire once, them stops firing. I've made a test case: <a href="http://irae.pro.br/jquerytests/live.html.html">http://irae.pro.br/jquerytests/live.html.html</a> The weird thing is that after the manipulation, if you stop modifying the DOM (use toggle link in test case), both handlers fire again. I dug into jQuery source but
1.3b2 live event delegation - callback not firing when bound to more than one event
If the same callback function is bound to more than one jQuery live event it will only fire for the last registered event. version: jQuery v1.3b2pre rev 6052 ticket: http://dev.jquery.com/ticket/3787 test page: http://csytan.googlepages.com/livetest.html Thanks for the great update, Chris
range selections is failing in 1.3 beta 2
http://dev.jquery.com/ticket/3813 It seems, that there's a selector regression in 1.3 beta2 $('div').filter(':gt(0):lt(5)') works well in 1.2.6, but return zero objects in 1.3b2 I don't know if it's already been discussed.
.live() delegation fails in second handler if first handler modify the DOM
I'm using 1.3b2 (6070) and found the following behavior. - using 2 .live() handlers for same link. - 1st handler always fire and modify the link with .html(string) - 2nd handler fire once, them stops firing. I've made a test case: http://irae.pro.br/jquerytests/live.html.html The weird thing is that after the manipulation, if you stop modifying the DOM (use toggle link in test case), both handlers fire again. I dug into jQuery source but was unable to solve the problem myself to present a patch.
don't work colspan when use .toggle("slow")
i need to show the "Subtable" table, when i use only .toggle() it work fine but when i use .toggle("slow") , the colspan attribute don't work anymore. i don't know if something is missing thanks for any help. this is the example HTML <table> <tr id="mainTable"> <td>text1</td> <td>text2</td> <td>text3</td> <td>text4</td> </tr> <tr id="SubTable"> <td colspan="4"> <table> <tr> <td></td> <td>text1</td>
1.3b2 - live event delegation doesn't work with objects
I searched in this mailing list and other also bug tracker but cannot find a discussion of this. There's no documentation for the live method so I assume this is a bug. Here's the simplest case $(function(){ // this does not work $(document.body).live('click',function(){ alert('works!'); }); // this doesn't either $($('body')).live('click',function(){ alert('works!'); }); // this works $('body').live('click',function(){ alert('works!'); }); });
'change', 'update' events not firing for jQuery UI 1.6rc4 and jQuery 1.3b2
I'm using a slightly modified version of the UI Sortable Layout demo and the 'change' and 'update' events for Sortable are not firing with jQuery 1.3b2. Changing the script tag to point at jQuery 1.2.6 fixes the problem. Is this a regression?
.clone Bug and feature suggestion
First for the bug. This bug has already been submitted(Ticket number 3500) and it seems like the fix suggested(removing lines 278 -291) fixes the issues in IE 6 and IE 7. Is this planned to be fixed for jQuery 1.3 because a few of my plug-ins required the moved version of jQuery to run this(and i have yet to see any issues in IE 6 or IE 7 when removing the suggested code). It would be great to hear an update on this ticket as it seems like a pretty big bug(at least to me this this function is very
'nodeType' is null or not an object, IE (all), jquery 1.2.6
hi, i get the following error on IE (6,7,8) with jquery 1.2.6: "'nodeType' is null or not an object" it seems to happen when cloning the object. no errors on firefox. maybe (still) a bug? found this info: http://groups.google.com/group/jquery-dev/browse_thread/thread/020197b99694915f CODE Snippet: //remove current properties-div, if minus-symbol was clicked //add new properties-div with default values, if plus-symbol was clicked $("#properties > div a img").mouseup(function(e){ var
xml is case sensitive
Hi jQuery dev, First post--haven't read or searched the group so forgive me if this has been mentioned. Anyway, xml is case sensitive, so jQuery breaks with content that is rendered application/xml+xhtml because jQuery assumes capital letters in the HTML dom's implementation with respect to the property nodeName that is bound to elements. Thanks Nour
is support for $.live(fn) planed?
I was looking for replacement for $(sel).livequery(function() {}) in 1.3b2 but it seems not to be planed. Since most of the livequery functionality will become obsolete by .live () may be this also could be covered? If so, porting a site with livequery+jquery1.2.x to jquery1.3 would be as simple as add the folowing lines: jQuery.fn.extend({ livequery:function() { return jQuery.fn.live.apply(this, arguments); }, expire: function() { return jQuery.fn.die.apply(this, arguments);
1.3beta 2 $().load() does not function if there is a hash in the url
Hello, Internet explorer fails to load a url that contains a hash. See: http://pixeline.be/experiments/jquerybeta/test2.html It does not work in 1.2.6 either, so it's probably related to a known IE shortcoming ? I lost a few thousand hairs before finding the cause of that load failure. HTH Alexandre
a change in bind?
Hi everyone! I'm testing 1.3 beta 2 with the project I'm working on... and noticed bind seems to act slightly different, compared to 1.2.6. In jQuery 1.2.6, bind accepts (type, [data], fn). This is the same in 1.3b2, except that it appears fn is passed three arguments instead of two. The new second argument seems to be the triggered binding's namespace. Example: If one wanted to bind to the tabsselect event (to perform an action when a tab is selected) in jQuery UI tabs, something like the following
Accordion on list with nested UL
Hi, I'm trying to use accordion with a Drupal book-menu list and it seems to fail with nested ULs. Out of the box the script opens sub- lists but then crashes after mousing off one of them. Are there limits on how lists can be built? This HTML is the default coming out of Drupal?! v1.6 Revision: $Id: jquery.accordion.js 4876 2008-03-08 11:49:04Z joern.zaefferer $ jQuery('#test ul').accordion({ active: false, // header: '.head', navigation: true, event: 'click', fillSpace: true,
:input doesn't match option
Hey guys, I figured recently that the :input selector matches select boxes but no options. Since we use it to cancel events in jQuery UI, some users reported select boxes not to work when draggables are used, for example. See the bug report here: <a href="http://dev.jquery.com/ticket/3791">http://dev.jquery.com/ticket/3791</a> Do you see any reason why adding <option> to the matched elements would be problematic? Thanks, Paul<br clear="all"> -- Paul Bakaus UI Architect -- <a href="http://paulbakaus.com">http://paulbakaus.com</a>
[jQuery] newbie code appraisal would be greatly appreciated
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> </head> <body bgcolor="#ffffff" text="#000066"> <div class="moz-text-plain" wrap="true" graphical-quote="true" style="font-family: -moz-fixed; font-size: 13px;" lang="x-western"> <pre wrap="">I've been getting into jQuery for my new site, and gotta say I love it, but wonder how I may better compress my code. If any kind souls can tip me off with a pointer or three, I'd be much, much, very much obliged. The site is <a class="moz-txt-link-freetext"
Porting a version of Mootool's Swiff
Hi, I am interested in getting involved in jQuery development, specifically, I would like to try to port the Swiff.js functionality from Mootools, as it allows for vastly superior interface with Actionscript. Has anyone attempted this, or are there any outstanding issues I should know about that would prevent this from happening? Thanks, -Dan
My take on jQuery UI
I believe the logic of jQuery is: jQuery('select something').doSomeAction() There are UI features that haven't been developed and are taking long but are very useful. Feautures like forms, grid, etc. I do not know if this have been thought about already or it is the way things are, but here is what I been thinking would make using jquery easier to use and maybe develop: Since we select HTML element/object(forgive my wording) which are already exists we could use already available HTML elements and
$('*').find(selector) is technically correct but
Out of curiosity, I did some test on jQuery.com On my console, I ran $("* div") Object length=25 $("div") Object length=25 $("*").find('div'); Object length=116 The last one is technically correct but wouldn't it be more useful to make the array of elements unique?
:not filter is slow in Sizzle
I checked out the latest version of Sizzle and ran the 2 queries below in slickspeed against the W3C document. I originally began with body :not(div, span, li) but realized that jQuery 1.2.6 didn't support it. body :not(div) body :not(.example) They are a lot slower when compared to jQuery 1.2.6. Might this be related to the fact that :not in Sizzle accepts complex selectors? - Kean
Help Test jQuery 1.3 Beta 2
Beta 2 is now out - and we need help testing it! More information here: http://blog.jquery.com/2009/01/05/help-test-jquery-13-beta-2/ --John
$.grep performance improvement
Hi there, I'd like to propose a performance improvement to the "static method" jQuery.grep (1 code line and 1 comment line, just that): $.grep = function(elems, callback, inv) { // Returns using JS 1.6 native code, if appliable if (Array.prototype.filter && !inv) return elems.filter(callback); var ret = []; // Go through the array, only saving the items // that pass the validator function for ( var i = 0, length = elems.length; i < length;
Bug: 1.3_b1 selector [nodeType=3] not working
This html: <body> <div id="demo">Lorem ipsum dolor sit amet.</div> </body> This jQuery: $(document).ready(function(){ alert($('#demo').contents().filter('[nodeType = 3]').length); alert($('#demo').contents().filter('[nodeType=3]').length); }); both alerts are 1 in 1.2.6, 0 in 1.3_b1 Thanks, Marion
newbie code appraisal greatly appreciated
I've been getting into jQuery for my new site, and gotta say I love it, but ... ... hmmn... I could probably compress my code, and wondered if any kind souls could tip me off with a pointer or three. Much, much, very much obliged. Olly the_guv guvnr.com The site is http://guvnr.com My jQ is (hopefully fairly self-explanatory) ... (html follows) ... jQuery.noConflict(); // *** POPUPS/SERVICE PANELS *** (this largest section of code controls my tab panels for the sections titled Web, Content, PC, Blog,
Tabindex Normalization for 1.3
I just attached a patch for ticket <a href="http://dev.jquery.com/ticket/3649">http://dev.jquery.com/ticket/3649</a> to fix getting and setting tabindex in IE. I'm hoping the patch can be reviewed and committed for 1.3.
1.3b1 selectors with complex attribute values
I have some complex values in markup that I use to traverse the DOM with $([attr=value]) but some complex values that work in 1.2.6 are not working in 1.3b1. I made a test case: http://irae.pro.br/jquerytests/1.2.6.html <-- works http://irae.pro.br/jquerytests/1.3b1.html <-- doesn't work As far as I could tell the problem is in the Sizzle chunker regexp, but I didn't have the time to try fixing it, so it can be other thing.
jQuery v1.3b1 bug? in animate callback
I boiled it down as much as I could. Test case is here: http://newlevant.com/marion/jqueryplugins/concentrationBug/ Calling animate like so: animate({opacity: 1.0}, flip.time, function () { ... }); And if flip.time is 0, subsequent calls don't wait for the animation to finish before calling the animate callback. Have not submitted a bug report (new to the whole system), but will if you think I should. (jQuery is fabulous by the way. Plugin where I found this bug is here: http://newlevant.com/marion/jqueryplugins/concentration/
build.xml uses YUICompressor(with patch)
http://dev.jquery.com/ticket/3779 http://dev.jquery.com/attachment/ticket/3779/build.diff
ATTR-Selector?
Hi, I test 1.3.b1 and this Selector work any more: <script type="text/javascript"> //<![CDATA[ $(document).ready(function() { // no more with 1.3b1 // $("#content a[href$='.jpg']").lightBox(); $("#content a").lightBox(); }); //]]> </script> What is to do? Thanks.
[jQuery 1.3b1] Name selector with a context doesn't work (patch and ticket inside)
I ran into this bug while testing 1.3 beta 1. In short, a selector like this: $('input[name=foo', '#form'); => Throws a context.getElementsByName is not a function error. More details (patches + tests) are in the Trac ticket: http://dev.jquery.com/ticket/3741 Cheers and thanks for jQuery as always, Chu Yeow
Can we remove the "extra" function from jQuery.trigger ?
Hi I've been watching this magic argument over and over, hoping it'd disappear. It seems it is used all over within jQuery UI but... according to Scott, it's encapsulated into one single function. So... IF we don't need it anymore on jQuery UI... can we just remove it from jQuery.trigger ? Anyone objects ? Also, but with less expectations, removing getData and setData would be nice IMO. I'm not so sure about this because I suppose some people actually rely on them, but they're nasty. They make $.data
.live issues.
http://labs.cloudream.name/jquery/live/ .live doesn't support selector "ol > li" or "ol li",(I miss something?) and event "mouseenter" (but not a bug I think) more details is in source code.
Coda Slider IE issues
Hello all, Having a bit of an issue with ie6 here. http://www.carlblackkennesaw.com/research-vehicles.jsp After the page fully loads, the coda script doesnt get rid of the scroll bars. This only happens in IE6. Other browsers seem to be fine. Any ideas what could be causing this issue? One thing that doesn't make sense to me is our homepage also uses the same slider but this issue doesn't happen on the homepage. Thanks in advance.
Creating a Firefox Addon with jQuery
Is it possible to use jQuery to create a Firefox Addon without causing any problems with others? I know Prototype.js causes problems since it extends native JavaScript classes such as Object and Array and those screw up for in loop used in other addons.
Creating Firefox 3 Addon with jQuery
Is it possible to use jQuery to create a Firefox Addon without causing any problems with others? I know Prototype.js causes problems since it extends native JavaScript classes such as Object and Array and those screw up for in loop used in other addons.
bug? in 1.3b2
jQuery v1.2.6: $('<div>a</div><div>b</div>').not(':eq(1)').length = 1 jQuery v1.3b2: $('<div>a</div><div>b</div>').not(':eq(1)').length = 2 example is a reduction of line 287 in http://jqueryjs.googlecode.com/svn/trunk/plugins/tabs/jquery.tabs.js : containers.filter(':eq(' + settings.initial + ')').show().end().not(':eq(' + settings.initial + ')').addClass(settings.hideClass); Thank you, -will
Next Page