[jquery-dev] Re: jQuery 1.3.2 Alpha Ready

2009-02-20 Thread seasoup
Is 1.3.2 released? There's been no announcement but the jQuery home page says Current Release: v.1.3.2 and it says 1.3.2 in the file that downloads... On Feb 19, 8:36 am, John Resig jere...@gmail.com wrote: I've filed a bug and will be following up:http://dev.jquery.com/ticket/4195 --John

[jquery-dev] Re: jQuery 1.3.2 Alpha Ready

2009-02-19 Thread lhwpa...@googlemail.com
i have found a bug in the 1.3.2 alpha. when i clone one or more selected option from one select to another there are differences between IE and firefox. in IE the cloned element (in the second select) stays selected. in firefox the cloned element is not selected. so which one is correct? the

[jquery-dev] Re: jQuery 1.3.2 Alpha Ready

2009-02-19 Thread John Resig
I've filed a bug and will be following up: http://dev.jquery.com/ticket/4195 --John On Thu, Feb 19, 2009 at 6:26 AM, lhwpa...@googlemail.com lhwpa...@googlemail.com wrote: i have found a bug in the 1.3.2 alpha. when i clone one or more selected option from one select to another there are

[jquery-dev] Re: jQuery 1.3.2 Alpha Ready

2009-02-17 Thread John Resig
I just tested and it's working again after some of the recent changes: http://jsbin.com/ajuja Thanks for the test case! --John On Tue, Feb 17, 2009 at 12:11 PM, Nikola nik.cod...@gmail.com wrote: I tried out a few things with 1.3.2pre and noticed that the Dialog window doesn't open in

[jquery-dev] Re: jQuery 1.3.2 Alpha Ready

2009-02-16 Thread Diego Perini
John, thank you for the nice additions and fixes, the document order is really welcome :-) Just a minor thing I noticed in the new code source is about older Opera (probably 9.27 and older). Opera have implemented the sourceIndex property too but it starts at index 0 for the documentElement. So

[jquery-dev] Re: jQuery 1.3.2 Alpha Ready

2009-02-16 Thread Brandon Aaron
Whoops... spoke to soon. The show method is throwing errors in IE 6. The main issue is that IE 6 doesn't like setting this[i].style.display to undefined. Second, it looks like the second for loop is sitting within the first for loop when I believe the intention was to have them separate, not

[jquery-dev] Re: jQuery 1.3.2 Alpha Ready

2009-02-16 Thread John Resig
The dual loop is actually a huge speed-up. If we set the display inside the first loop (and then check the computed display of the next element) this causes a fresh reflow of the page. For every single element that we show/hide. Last check this is giving us a 2x speedup (even with the extra loop

[jquery-dev] Re: jQuery 1.3.2 Alpha Ready

2009-02-16 Thread mike.helgeson
How many days, do you reckon, from alpha until release for 1.3.2? On Feb 16, 5:30 pm, John Resig jere...@gmail.com wrote: It's not supported but a swtch to a typeof check seems simple enough. Thanks for the tip. --John On 2/16/09, Diego Perini diego.per...@gmail.com wrote: John,

[jquery-dev] Re: jQuery 1.3.2 Alpha Ready

2009-02-16 Thread Brandon Aaron
Do you still have those speed tests for this around. I'm more curious why it speeds things up than anything else. I understand why it speeds things up in hide... just not understanding how we are gaining any performance in show. -- Brandon Aaron On Mon, Feb 16, 2009 at 4:26 PM, John Resig

[jquery-dev] Re: jQuery 1.3.2 Alpha Ready

2009-02-16 Thread Matt
On Feb 16, 12:31 pm, John Resig jere...@gmail.com wrote: There were some logic changes ... how :visible/:hidden work Previously, elements with visibility:hidden were not :visible, but now they are (tested in IE6,FF3). Was this an intentional change? Matt Kruse

[jquery-dev] Re: jQuery 1.3.2 Alpha Ready

2009-02-16 Thread John Resig
Depends how many bugs are spotted - hopefully not many. --John On Mon, Feb 16, 2009 at 5:36 PM, mike.helgeson mike.helge...@gmail.com wrote: How many days, do you reckon, from alpha until release for 1.3.2? On Feb 16, 5:30 pm, John Resig jere...@gmail.com wrote: It's not supported but a

[jquery-dev] Re: jQuery 1.3.2 Alpha Ready

2009-02-16 Thread John Resig
Previously, elements with visibility:hidden were not :visible, but now they are (tested in IE6,FF3). Was this an intentional change? Yes. Previously bugs would occur with methods like height/width, hide/show, and animate (which only operated on the display property) but the :visible and