Thank you for all the suggestions. Yes, we are most definitely looking at
ways to rein in the big select lists, but that won't happen overnight,
unfortunately. I would argue that hundreds of nodes is fairly big, but not
big enough to explain it taking 12+ seconds to process, especially when the
!= 'hidden'
fields[i].style.display != 'none'
!fields[i].disabled)
{
fields[i].focus();
break;
}
}
On 12/20/06, Todd Menier [EMAIL PROTECTED] wrote:
Thank you for all the suggestions. Yes, we are most definitely looking at
ways to rein in the big select lists
Hello,
I'm writing a function in a global script that will apply focus to the first
visible enabled form field on a page. I'm using the following jQuery
expression to find the control:
$('#mainContent
:input:visible:not(:checkbox):not(:button):not(:submit):not(:image):not([EMAIL
();
});
On 12/19/06, Todd Menier [EMAIL PROTECTED] wrote:
Hello,
I'm writing a function in a global script that will apply focus to the
first visible enabled form field on a page. I'm using the following jQuery
expression to find the control:
$('#mainContent
:input:visible:not(:checkbox
, Brandon Aaron [EMAIL PROTECTED] wrote:
If you can, grab the latest from SVN because it is fixed there.--Brandon AaronOn 11/7/06, Todd Menier [EMAIL PROTECTED] wrote: Hello, I'm hoping someone might be able to offer some insight into a rather urgent
issue I'm struggling with. I'm using jQuery
Since I'm usually taking a lot more from this group than I'm giving back, I thought I'd offer this up if anyone might find it useful. It's a simple global object for tracking code execution time. (I discovered Firebug's console.time
after I'd already written this. Oh well. This one can be used in
Since I'm usually taking a lot more from this group than I'm giving back, I thought I'd offer this up if anyone might find it useful. It's a simple global object for tracking code execution time. (I discovered Firebug's
console.time
after I'd already written this. Oh well. This one can be used
Hello,The following test code moves 2 form elements from one location in the DOM to another. Both elements retain their state just fine in FireFox, but in IE the current state of the checkbox is lost when the element is moved:
script$(function() { $('#btn').toggle( function() {$('#d1
').toggle(move('#d1', '#d2'), move('#d2', '#d1'));
});On 10/12/06, Klaus Hartl [EMAIL PROTECTED] wrote:
Todd Menier schrieb: Hello, The following test code moves 2 form elements from one location in the DOM to another. Both elements retain their state just fine in FireFox, but in IE the current state
Awesome, thanks so much!On 10/7/06, Mike Alsup [EMAIL PROTECTED] wrote:
Todd,Just tack ?format=txt on to the end of the url.For example,http://jquery.com/dev/svn/plugins/form/form.js?format=txt
Mike___jQuery mailing
Hello,I've been poking around a bit in the jQuery source code. It's been enlightening and has proven that I don't know as much about _javascript_ as I thought I did!Here's a pattern that occurs frequently that I'm really curious about:
new function() { // do stuff}Is the purpose of this just to
Michael Geary [EMAIL PROTECTED] wrote: See if this helps: function Stuff() { // do stuff } var stuff1 = new Stuff(); // call the Stuff constructor
var stuff2 = new Stuff; // parens are optionalThanks, the aha! light just went on. It makes total sense now...I didn't know you could call a
Thanks for pointing that out, I did look at it when it came out but sort of forgot about it. I initially dismissed it because seemed like it had too many bells and whistles and was much too slow, but that cetainly could be a server issue and not a problem with the plugin. I'll give it another look
13 matches
Mail list logo
