multiple-descendant selector bug in 1.3
<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Devs,<div> </div><div>Just wanted to call your attention to a rather lengthy thread on the jquery-en list:</div><div><a href="http://groups.google.com/group/jquery-en/browse_thread/thread/1c6403c5f628d45a">http://groups.google.com/group/jquery-en/browse_thread/thread/1c6403c5f628d45a</a></div><div> </div><div>The upshot of it is, I think, a bug when multiple descendants appear in a selector. </div><div>
jQuery 1.3 Released
Hey Everyone - jQuery 1.3 is out! Full details here: http://blog.jquery.com/2009/01/14/jquery-13-and-the-jquery-foundation/ Happy 3rd Birthday, jQuery! --John
<span> with single space: broken in ie, works in firefox, safari
$('<span> </span>').contents().length is 1 in firefox and safari, 0 in ie (6 & 7). (maybe hard to read: this is a span containing a single space) I have a work-around: $('<span/>').text(' ').contents().length is 1 everywhere. jQuery 1.2.6 & 1.3 both. Marion
DOM-triggered events versus .trigger()
I was looking at this ticket and just attached a test case: http://dev.jquery.com/ticket/3827 In the test, you can uncomment the lines to have the handlers return false and prevent the default action, which would be to toggle the checkbox state. In jQuery, trigger() calls the handler before the default action is taken. The check box is in its previous state, the one before the click. If the handler returns false and/or uses preventDefault, jQuery will not call the DOM element's click() method. Otherwise
Suggestion: Deactivate Explorer's Alpha filter when opacity is set to 1.0
jQuery supports automatically using Explorer's Alpha filter for setting an elements opacity, ie. when doing css('opacity', '0.5'). Explorer's filters have varying degrees of side effects, and to minimize these I suggest automatically disabling the Alpha filter as well when the opacity is set to 1.0, which equals no opacity anyway. One can do this manually with css('filter', "alpha(enabled='false')"), but I think jQuery just as well could do this automatically since it already implisitly activates
clone(true) inconsistency
Hi, Noticed this discrepency between versions 1.2.6 and 1.3: $(selector).prepend(element.clone(true)); where the selector grabs >1 elements. In 1.2, every element gets the cloned element with its events. In 1.3, only the first element selected gets the events, all the others just get a copy, as if it had been made with clone(). btw I've amended my code to $(selector).each(function() { $(this).prepend(element.clone (true)); }); so it's no Big Deal, but I think 1.2's behaviour was less surprising than
datepicker position
Hi guys, I think the function _checkOffset is failing, in all browsers. Whenever open a datepicker when my browser window is scrolled down and/ or right, it draws the datepicker too high and/or left, often I have to scroll to find it. I checked this with svn checkout and it still fails, even with the packaged demo. Opened a ticked for this yesterday (#3863). Anybody not have this problem, or aware of it already? thanks, Jez.
Unbind'ing events declared in tag.
If an event is defined in a tag, say <img onclick="alert('Sneh');" />, then $(img).unbind() has no effect on the onclick attribute. I have to go in an set the onclick="". Is this expected behavior?
IE and jQuery cache
Hallo , ich finde bei Problem im jQuery keine Lösung. Der IE führt Anweisungen wie zB. $( "#" + cb1 + ", #" + cb2).attr("checked", bChecked); nur mit sichtbarer Verzögerung aus. Beim debuggen hab ich dann festgestellt, dass das Objekt $.cache ordentlich "vollläuft". Jetzt hoffte ich, dass $.cache = {} Abhilfe schafft, doch leider führte das dann zu dieversen Einschränkungen im bisherigen Eventhandling. Zwar war der IE danach rasend schnell, aber verschiedene Events wurden anschließend nicht mehr
Bugs of Is( ) in jquery 1.3 , it can't work well,always return True
I want to make such effect as when click even table row,it's background will turn green. when click odd table row,it's background will turn red. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <script src="http://code.jquery.com/jquery-latest.js"></script> <script> $(document).ready(function(){ $(".stripe tr").click( function(){ if($(this).is(".stripe tr:even")) $(this).css("background","green"); else $(this).css("background","red");});
live() don't trigger first assigned event on multiple event binding
While palying around with the latest svn build of jquery I noticed that .live is don't triggering the first assigned event, if you pass a list of events to the first argument like you can do so with bind. Every event is triggered except the first assigned even if you pass all the supported events to .live. Example: $("selector").live("dblclick mousedown click", function(e) { } ); Here mousedown and click will be triggered, dblclick will be not. You can find a complete test case here: http://blog.metaen.de/static/sites/livebug/index.html
Regression jQuery UI 1.6rc4 + jQuery 1.3 : triggerHandler problems
I'm not very certain about the origin of this problem, but it appears that when using the last release candidate of jQuery-UI with the last official release of jQuery, triggerHandler causes some problem. Try to create a simple slider with a callback on "slide". Tell me if the callback is triggered when moving the handler
Selector attribute filter bug in 1.3?
The documentation for the [attr!=value] filter reads: "Matches elements that either don't have the specified attribute or do have the specified attribute but not with a certain value." In 1.2.6 $("li[class!='zoom']") would give me both LI elements without a class attribute and those with a class attribute not equal to 'zoom'. In 1.3 I only get LI elements with a class attribute defined (and not equal to 'zoom'). To me this seems like a bug, and not the best behaviour. It's also in conflict with the
$('div:has("p+p')') causes browser to freeze with jQuery 1.3
I get: "A script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger, or let the script continue." With the code: $('div:has("p+p')') And the HTML: <div> 1</div> This worked fine with jQuery 1.2.6. Test case: http://jsbin.com/atiha/edit Tested in FF3, IE7 and Chrome. Is this a bug with jQuery 1.3 or is the syntax wrong?
:eq(n) issue
I think there is an issue with :eq(). Demo test case http://jsbin.com/omobe
What about a first-parent ?
Hi, Example : I have list into other list, in few LI element I've got input. I want to take all input element which have the class "toto" and remove the LI which is the parent of the input (not the direct ancestor ;)). So it will be good if I could do something like: $('input.toto').parents('li:first-parent').remove(); What about that please ?
more selector regressions in 1.3rc2 - Safari capital letters in class names
I'm seeing very odd behavior in Safari with selecting class names that include upper case characters. I just filed http://dev.jquery.com/ticket/3840, but here's the deal in the test code below: the selector for $ ("#ALLCAPS") works fine, but $(".ALLCAPS") returns nothing. This is with Safari Version 3.1.2 (5525.20.1). Everything works fine in FireFox, and this worked fine in 1.2.6. It appears a single capital letter in a class name triggers this behavior. Clearly a HUGE bug unless I'm missing something.
1.3rc2: animate with duration of 0 and callback << bug
1.3rc2: animate with duration of 0 and callback << bug Something goes wrong in jQuery-1.3rc2.js with animate when duration is 0, and there is a callback. Is 0 an illegal duration? If not, there's some bug in the jQuery code. code: $(document).ready(function(){ doFades([ {f: '#c0', s: 0}, {f: '#c1', s: 1000}, {f: '#c2', s: 1000} ]); }); function doFades(fades) { var fade; console.log(fades); if (fades.length === 0) { return; } fade = fades.shift(); $(fade.f).animate({opacity: 0.1}, fade.s, false,
quick question about closest(), also...nextest() or similar?
i've been using chains like this all over my webapp: $(this).parents("li:eq(0)") it seems that closest is a direct replacement for this and a functional equiv of $(this).closest("li"). also, is there anything like nextest() that works outside the bounds of the parent container? for example: <span> <b id="foo">bar</b> </span> <span> <b>Hello!</b> </span> $("#foo").nextest("b") would return the second <b> node in the tree following the current element, but not a sibling. right now i'm needing to create
Regression: parents with expression finds no matches. May only affect XHTML.
Test case: http://intertwingly.net/stories/2009/01/14/test12.html http://intertwingly.net/stories/2009/01/14/test13.html - Sam Ruby
$.ajax option "timeout" not working, bug?
I tried using the timeout option on $.ajax and it just didn't seem to work. I think I tracked it down, since xhr gets set to null in onreadystatechange( "timeout" );, if ( xhr ) xhr.abort(); never runs and therefor the ajax call never gets cancelled. Is this a bug or is it how it is meant to work? It works (closes the connection) if you move xhr.abort(); before running onreadystatechange. Line: 3486 if ( s.async ) { // don't attach the handler to the request, just poll it instead var ival
significant $.val() regress bug on <select> elements in v1.3!
.val() now returns undefined if <option> elements contain a "value" attribute, otherwise val() returns text() of the :selected option. both actually seem incorrect to me but only the first behavior seems like a blocker regress. i first noticed that it was strange that the "single select" example for val() contains no "value" attributes, and instead returns text() if they are not present. http://docs.jquery.com/Attributes/val i just ran into this during my webapp port. testcase: http://www.thermosoft.com/test/select-val-bug.php
jquery 1.3 select elements
I cant seem to set the value of any select elements using val. Input type=text is working fine. So I have something like: $('#usa_reference_state_id').val("2") alert($('#usa_reference_state_id').val() ) and the alert is "" so no value was set. I am 100% sure that 2 is in the list of options for #usa_reference_state_id.
$(document) undefined
Hi, I am facing a issue that says, $(document) is undefined in IE and the code does not work in the and no error shows up in firefox. I saw the script and opened the script file in browser and it opened up so that means it is getting the js file yet it is giving the error. :Ajay
Why doesn't focus() trigger a blur?
I've only just noticed this, but the jQuery focus() method doesn't cause a blur event to trigger on the previously focused element. The code below demonstrates. You need to focus a list item by clicking on it and then using the up/down arrows to move the focus. The actual focus is moved as shown by the yellow background from the li:focus css rule, and the focus event is triggered as shown by the bold text. But the blur event is not triggered on the previous item. Clicking on another item will focus
Delegation: Bind and Is or Live
Hello, Sorry of this comes across as a silly question but I was wonder which is the better approach (or are they essentially the same thing?). Description - A div called skill-list houses hundreds of drop downs with the class skill-level-selector. When one of these selcts are changed an ajax call is made. Code below -- $('.skill-level-selector').live("change", function(){ $.post( 'someUrl', { skillId: this.id.split('-')[2], level: $(this).val() }, function(data, textStatus){ } ); }); ---- OR ----
enhancement proposal for .animate()
Hi there, The last year I had to make a lot of animation with jquery and I ended up including custom plugins and extensions for adding support to animate from one class to another and to have a delay. All the plugins in the jquery plugin repository to do this are not documented quite well and the result when using these to enhancements together is quite messy. So I'd like to propose to include these to enhancements into the core. animate( .classname | style rules , [duration], [easing], [callback],
jQuery 1.3rc2 Ready
Hey Everyone - jQuery 1.3rc2 is ready. This means that 1.3 is effectively finished barring a horrible bug between now and the final release on Wednesday (the 14th). You can grab the source here: http://code.jquery.com/jquery-1.3rc2.js Please let me know, personally, if you find some bad new bug and we can triage it together. A screenshot of the final test run can be found here (on 8 browsers): http://www.flickr.com/photos/jeresig/3192101251/ A couple bugs were found in last night's rc1 one (a problem
Access next tag
Hi, I have a requirement in which I need to access the next element. like <div class="a"> <div class="b"> <div class="e"></div> </div> <div class="c"></div> </div> Now this structure is repeated, what what I want is on click of "e" I need to toggle appearance of "c" based on which "e" has been clicked because this structure is repeating I can not specify Id to div's. so how can I get this functionality?
1.3 RC2, selecting options
I'm currently adapting the validation plugin to 1.3 RC2, aiming for a new release before 1.3 is out. The obvious problem, usage of deprecated [@attr=val] selectors was easy to fix. Another issue I couldn't fix yet is selecting options. I'm using these lines to validate if enough options have been selected: var options = $("option:selected", element); return options.length > 0 && ( element.type == "select-multiple" || ($.browser.msie && !(options[0].attributes['value'].specified) ? options[0].text
$.live performance and multi-container mousemove delegation?
I may soon need to track mouse movements in various multiple containers in a webapp. I was wondering if using $.live would be impractical in this scenario since $.live binds to document and may degrade performance if you need to track numerous mousemove events but only inside a limited area. would it not be much better to explicitly specify containers in this case to prevent significant performance degradation involved with doing so much filtering regardless of cursor position within the document?
Possible selector regression in 1.3rc2
Hey guys, when investigating why some of the jQuery UI demo pages didn't work with 1.3rc2, we found out it's related to 1.3rc2: We were doing the following: $('> :eq(0)', context) this worked in 1.2.6, in 1.3 you receive: Syntax error, unrecognized expression: > The bug only happens if 1) The first character is > 2) the immediate following part is a pseudo-selector (i.e. "> *:eq(0)") 3) The pseudo-selector has brackets (i.e. "> :input" works) This is definitely a regression. Any ideas?<br clear="all">
.find(':first-child') vs .children(':first') in 1.3rc2
Hey, I've seen different behavior with these two functions in my application after switching from 1.2.6 to 1.3rc2. I haven't been able to come up with a test case, but I think it's related to append, prepend,before and after (which is what I use before doing calling .find()) Anyway, if anybody else has run into this and knows the explanation I would really appreciate it. If you have been running into problems and your application uses something like: $('.myClass').find(':first-child') use this instead:
RC2 'tolerance' bug
I had a bit of a mangled selector on one of my pages which 1.2.6 simply skipped over, but completely kills 1.3. In fact helped me spot a bit of code that had never worked. Full test case here: https://www.partyark.co.uk/html/jquery1.3rc2-bug.html
$().remove() generate error in IE6.
Hi, following code does not work in IE6 (FF3.0 works), anyone have this problem? $.debug(true); var d = parseXML("<x><y>yy</y><z>zz</z></x>"); $.log($("z", d).text()); $("z", d).remove(); $.log($("z", d).text()); After some debugging, it seems like the error occur at data: function( elem, name, data ) { elem = elem == window ? windowData : elem; var id = elem[ expando ]; // Compute a unique ID for the element if ( !id ) id =
jQuery-like smooth animate
Hi, group. Im trying to make animation using jquery, but thats controlled server side using XMLSocket. When jQuery receive coordinates from server it moving my DIV across the browser but its too fast(my server spit all the coordinates at once). I cant understand how to do smooth animation. My server script (perl) compute the same x,y coordinates like jquery (i saw how in jQuery core) but i dont know how jquery delay all these x and y coordinates properly to make animation smooth. Ill be happy if
1.3b2 selector engine *much* slower than 1.3b1 under FF 3.0.5
I noticed this while working on an in-house project. Note that the bug does not appear to affect FF 3.1, which probably means qSA handles whatever it is that changed well. I've hastily thrown up some quickie test cases. Version: jQuery v1.3b2 Ticket: http://dev.jquery.com/ticket/3819 Running FF 3.0.5: Using 1.3b1: http://doctyper.com/stuff/jquery/1.3b1.html Using 1.3b2: http://doctyper.com/stuff/jquery/1.3b2.html
jQuery 1.3rc1 : Error with :not()
Hi, I have 3 html TABLEs in my DOM $("table:not(:first)").length() gave me 2 (correct) tables in 1.2.6 gives me 5(???) tables in 1.3rc1 also, doesn't work the version: $('table').not(':first').length()
Taconite plugin reveals 1.3b2 regress bug (#3737) : (
malusp and i reopened this one, maybe you guys can take a look? pretty please? http://dev.jquery.com/ticket/3737
name="id' bug
Supposedly this issues was already fixed however with version 1.2.6, if i have a form element with the name of id, none of my jquery code executes. I have tested this in FF3, IE 6/7, Safari and and fails in all browsers. Is this issue known that it still exists? -- View this message in context: http://www.nabble.com/name%3D%22id%27-bug-tp21374362s27240p21374362.html Sent from the jQuery Dev List mailing list archive at Nabble.com.
Next Page