I am in the same boat (don't have the luxury of playing around).
Jörn's version has been pretty stable, with the exception of the
issues documented. The one problem I have is similar to yours, in that
IE6 generates an error when mousing over.the selection list.
Unfortuanely, at least 90% of the us
Will do what you suggested and get back to you.
On Jul 12, 4:18 pm, Jörn Zaefferer <[EMAIL PROTECTED]> wrote:
> Jeff Fleitz wrote:
> > So, for all you gurus out there, how do you track down this type of
> > issue in IE6? Since Firebug doesn't report an error, that doe
I am using Jörn's Autocomplete alpha plugin (not from the svn
repository) along with jquery 1.1.3.1 and am having some problems in
IE6 related to selected options from the drop downs. The autocomplete
control works fine if I use the down arrow to navigate to a choice.
However, if I use the mouse
> // remove selected items from the #mySelect element
> var oRemoved = $("option:selected", oSelect).remove();
>
> -- or --
>
> var oRemoved = oSelect.find("option:selected").remove();
>
How would you identify an individual option index using this syntax?
In other words if I wanted to check the v
> Now for Part 2 of the lesson. :)
>
> // remove selected items from the #mySelect element
> var oRemoved = $("option:selected", oSelect).remove();
>
That's the ticket! I had just finished caching the #mySelect
reference like that, and was just trying to figure out how to make
that call, but cou
>
> First off, always try to cache jQuery objects if you're planning on reusing
> them. This speed things up considerably, as jQuery doesn't have to keep
> doing the parsing.
>
Good point.
> With all that said, you should be able what you're wanting in one command:
>
> var oRemoved = $("#mySele
Hey Dan,
> Personally, I'd use $("#mySelect")[0].length, since it uses the actual DOM
> property for the element. This should be faster than parsing out
> the option tags that are selected.
>
Yep, I like that as well.
> However, the $("#mySelect option:selected") would allow you do other thing
Worked, thanks Dennis.
On May 7, 11:15 am, spinnach <[EMAIL PROTECTED]> wrote:
> try $("#mySelect")[0].length ...
>
I apologize in advance if this is in the docs, but I probably won't be
able to access the jQuery site for a while now that the ip has
changed, due to proxy issues.
I want to limit a user from entering more than a specified number of
options, and can't find the correct syntax (or maybe I can't do
That was it! It looks so simple. Thanks, Jörn.
I just received John Resig's Pro JS Techniques book, and plan on going
over this oop style js stuff and studying your examples, now that the
heat will be off.
Many thanks again.
On May 3, 12:24 pm, Jörn Zaefferer <[EMAIL PROTECTED]> wr
I thought I had it working, but I don't, I am still having issues. I
have two lookups on the same form, and the data is returned fine.
data[0] is the text description and data[1] is the primary key of the
lookup table. I am trying to pass the values to some hidden fields.
I am using the code blo
Nevermind, figured it out, thanks.
On May 2, 10:33 am, Jeff Fleitz <[EMAIL PROTECTED]> wrote:
> > Try $("#suggest2+pk").val( data[1] ) or $(this).next().val( data[i] );
> > And first check if the "#suggest2+pk" selector really selects your
> > hidde
> Try $("#suggest2+pk").val( data[1] ) or $(this).next().val( data[i] );
> And first check if the "#suggest2+pk" selector really selects your
> hidden input.
>
This technique worked great for populating a hidden field. I am
trying to use the same technique to add an option to a select control
in
Hey Dan,
I am playing around with your suggestions below on how to implement
multiple autocomplete calls on one form using your implementation. I
have added the second argument (input) in the callback as you
suggested, but am stumped about where in the code to pass the input
reference from? I hav
I'm confused. Which example are you referring to?
I would like to see for each text value selected in a multiple, the
associated pk in the db table associated in a delimited list, e.g.,
Item1,Item2, Item3
pk1,pk2,pk3
so that when we process the form input, we can reference by position.
Does th
$(this).next().val( data[i] ) worked Jörn, thanks.
Any idea how I would make this work when the multiple attribute is
used? Right now it will return only the last value selected. It would
be nice to capture all of the ids, delimited using the same
multipleSeparator value that the text area uses.
Hi Dan,
I am going to owe you some serious beer here pretty soon.
>
> >$("#suggest2").result(function(event, data, formatted) {
> >$(this).find("..+/input").val(data[1]);
> >});
>
> I believe the code above translates to my onFindValue. This means the above
> code is run when
I have been using Dan's version of autocomplete successfully on some
CF forms where I am querying some lookup tables, and passing primary
key values on to the action pages instead of the text description for
SQL inserts. I am to implement the same functionality in Jörn's
version, and cannot figure
t menu and uses your third option (disallowing the
already selected option to be selected again), and while it works
great, the users all commented they would rather not see the option
displayed once again, once it has been selected.
Jeff
On Apr 18, 1:28 pm, Jörn Zaefferer <[EMAIL PROTECTED]&g
Yeah, I found that. I was looking for 'transport' instead of 'xml'.
I believe I will leave it alone as I don't think it is causing me
problems.
Thanks all.
On Apr 18, 1:37 pm, Jörn Zaefferer <[EMAIL PROTECTED]> wrote:
> Dan G. Switzer, II schrieb:> Jeff,
>
> >> Boy I feel like a dummy, but I ca
Yeah, I had looked at that the iframe thing too after googling for
some answers, but I had played with iframes on another section of the
site, and never saw an issue, so I put that on the back burner.
I can't believe I didn't miss that cool gif image. I remembered seeing
it when I was doing your
My bad. You were right about 1) The culprit was the indicator.gif
file. I had moved the css file to a different folder and it broke the
reference.
Things are working now. Thanks.
Jeff
On Apr 18, 12:36 pm, "Dan G. Switzer, II" <[EMAIL PROTECTED]>
wrote:
> Jeff,
>
> >Yeah, thats what I did. Di
Yeah, thats what I did. Didn't work. Hmmm.
On Apr 18, 11:40 am, "Dan G. Switzer, II" <[EMAIL PROTECTED]>
wrote:
> Jeff,
>
> >What did you do to fix this issue?
>
> >$("#addunit_lookup").autocomplete(
> > "qryUnitLookup.cfm",
> > {
>
> I used the fully qualified URL. So instead of:
>
> qryUnitLo
What did you do to fix this issue? I am running into something
similar with IE 6 only. No issue in FireFox or IE 7. We are using PKI
certificates for the site, no Win authentication, and I get that
security dialog in IE that says "This page contains both secure and
nonsecure items. Do you to dis
Boy I feel like a dummy, but I can't even find that line in my jQuery
script. I am testing with jQuery 1.1.2 unpacked. Is that what we are
talking about? I might be having a similar problem and want to test
against that by commenting this out as well, but it helps if you can
find it first.
doh..
Nice job!
The multiple option is the bomb.
One thing that I think would be useful to add (I pinged Dan about this
the other day), is an option to restrict the multiple option to
distinct values, so that duplicate selections are prevented.
Jeff
On Apr 17, 5:04 pm, Jörn Zaefferer <[EMAIL PROTECT
Excellent, ideas Dan. Let me give that a shot.
I appreciate the effort on this, I know it was a lot to absorb.
Thanks!
Jeff
Hi Dan, guess I'll jump in real quick while the iron is hot.
I too am a noob to jQuery and Ajax stuff in general. I borrowed your
autocomplete example (and downloaded your recent presentation to check
out the other stuff), and I have it working great, including passing
the hidden id value, etc. A
28 matches
Mail list logo
