Re: [jQuery] Autocompleter update (again)
What problems are you seeing? http://www.dyve.net/jquery/?autocomplete seems fine to me right now on ie and ff -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dylan Verheul Sent: Thursday, September 07, 2006 10:41 AM To: jQuery Discussion. Subject: Re: [jQuery] Autocompleter update (again) The new code introduced layout quirks in Internet Explorer (and perhaps also Firefox). Maybe a wrapper DIV wasn't such a bad idea after all ... I don't want to make autocompleter dependant on another plugin (else I'd use Interface for position and size). Any suggestions? I think I'll go back to the wrapper DIV fo rnow to keep a working version online. On 9/7/06, Dylan Verheul [EMAIL PROTECTED] wrote: After all the IE transparecny issues, I decided to take a closer look at what I was doing at the DOM level, and I looked at solutions of other plugin authors. It turned out that I was using a workaround for a bug that existed in earlier versions of jQuery that had since been fixed. Also, the DatePicker plugin had a more elegant way of handling the IE transparency bug. So: - Autocomplete no longer uses a wrapper DIV - IE transparency issues seem resolved - The plugin file is smaller in size - I optimized some other stuff I tested in IE, Opera and Firefox. You will probably need to take a look at your CSS if you update to this newer version, espcially the iframe bit (see source code of my example page). I may include the iframe CSS hardcoded in a next release. http://www.dyve.net/jquery?autocomplete ( docs on the site ) ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/ ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
Re: [jQuery] Autocompleter update (again)
Yes, I updated the script. It's fine in simple layouts, but try it with a complex (liquid, no-tables CSS or stuff like that), and it's all over the place. It looks like I found a solution that works on Firefox and IE now. Opera is a little off. Suggestions welcome. On 9/7/06, Geoff Knutzen [EMAIL PROTECTED] wrote: What problems are you seeing? http://www.dyve.net/jquery/?autocomplete seems fine to me right now on ie and ff -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dylan Verheul Sent: Thursday, September 07, 2006 10:41 AM To: jQuery Discussion. Subject: Re: [jQuery] Autocompleter update (again) The new code introduced layout quirks in Internet Explorer (and perhaps also Firefox). Maybe a wrapper DIV wasn't such a bad idea after all ... I don't want to make autocompleter dependant on another plugin (else I'd use Interface for position and size). Any suggestions? I think I'll go back to the wrapper DIV fo rnow to keep a working version online. On 9/7/06, Dylan Verheul [EMAIL PROTECTED] wrote: After all the IE transparecny issues, I decided to take a closer look at what I was doing at the DOM level, and I looked at solutions of other plugin authors. It turned out that I was using a workaround for a bug that existed in earlier versions of jQuery that had since been fixed. Also, the DatePicker plugin had a more elegant way of handling the IE transparency bug. So: - Autocomplete no longer uses a wrapper DIV - IE transparency issues seem resolved - The plugin file is smaller in size - I optimized some other stuff I tested in IE, Opera and Firefox. You will probably need to take a look at your CSS if you update to this newer version, espcially the iframe bit (see source code of my example page). I may include the iframe CSS hardcoded in a next release. http://www.dyve.net/jquery?autocomplete ( docs on the site ) ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/ ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/ ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
Re: [jQuery] Autocompleter update (again)
The new code introduced layout quirks in Internet Explorer (and perhaps also Firefox). Maybe a wrapper DIV wasn't such a bad idea after all ... I don't want to make autocompleter dependant on another plugin (else I'd use Interface for position and size). Any suggestions? I think I'll go back to the wrapper DIV fo rnow to keep a working version online. On 9/7/06, Dylan Verheul [EMAIL PROTECTED] wrote: After all the IE transparecny issues, I decided to take a closer look at what I was doing at the DOM level, and I looked at solutions of other plugin authors. It turned out that I was using a workaround for a bug that existed in earlier versions of jQuery that had since been fixed. Also, the DatePicker plugin had a more elegant way of handling the IE transparency bug. So: - Autocomplete no longer uses a wrapper DIV - IE transparency issues seem resolved - The plugin file is smaller in size - I optimized some other stuff I tested in IE, Opera and Firefox. You will probably need to take a look at your CSS if you update to this newer version, espcially the iframe bit (see source code of my example page). I may include the iframe CSS hardcoded in a next release. http://www.dyve.net/jquery?autocomplete ( docs on the site ) ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
Re: [jQuery] Autocompleter update (again)
I've tried the latest version right now, sometimes I get Errore: uncaught exception: Permesso negato per ottenere la proprietà HTMLDivElement.parentNode in my js console, that sounds like Access denied to obtain the property HTMLDivElement.parentNode btw the problem of two nested divs I explained in my previous post has disappeared. 2006/9/7, Dylan Verheul [EMAIL PROTECTED]: After all the IE transparecny issues, I decided to take a closer look at what I was doing at the DOM level, and I looked at solutions of other plugin authors. It turned out that I was using a workaround for a bug that existed in earlier versions of jQuery that had since been fixed. Also, the DatePicker plugin had a more elegant way of handling the IE transparency bug. So: - Autocomplete no longer uses a wrapper DIV - IE transparency issues seem resolved - The plugin file is smaller in size - I optimized some other stuff I tested in IE, Opera and Firefox. You will probably need to take a look at your CSS if you update to this newer version, espcially the iframe bit (see source code of my example page). I may include the iframe CSS hardcoded in a next release. http://www.dyve.net/jquery?autocomplete ( docs on the site ) ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/ -- kain kuht.it ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
Re: [jQuery] Autocompleter update (again)
2) Is there something I can add to programmatically disable the default forms-autocomplete function in browsers? FF's default menu choices are competing with the plugin's choices. for mozilla browsers set an attribute autocomplete to off! -- klaus ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
Re: [jQuery] Autocompleter update (again)
Works for IE, too: http://msdn.microsoft.com/workshop/author/dhtml/reference/properties/aut ocomplete.asp Here's a good backgrounder document: http://wiki.mozilla.org/The_autocomplete_attribute_and_web_documents_usi ng_XHTML ~ David -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: September 7, 2006 1:48 PM To: jQuery Discussion. Subject: Re: [jQuery] Autocompleter update (again) 2) Is there something I can add to programmatically disable the default forms-autocomplete function in browsers? FF's default menu choices are competing with the plugin's choices. for mozilla browsers set an attribute autocomplete to off! -- klaus ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/ ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
Re: [jQuery] Autocompleter update (again)
1)
Make sure that the input element has the rule display: block
.ac_wrapper input {
width: 100%;
display: block;
}
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Jason Huck
Sent: Thursday, September 07, 2006 1:39 PM
To: discuss@jquery.com
Subject: Re: [jQuery] Autocompleter update (again)
This looks pretty nice. Attempting to implement now, got a couple of
questions:
1) Using the CSS in your demo page, what's the easiest way to nudge the
entire results list down a bit? For some reason mine are popping up directly
over the input element instead of just beneath it, obscuring it.
2) Is there something I can add to programmatically disable the default
forms-autocomplete function in browsers? FF's default menu choices are
competing with the plugin's choices.
3) Also, a note: On my test page I have a div with overflow set to auto. The
scrollbar in that div is bleeding through the autocomplete menu.
This is all in Firefox 1.5.0.6/Mac. Haven't gotten any further than that
yet.
Thanks!
Jason
--
View this message in context:
http://www.nabble.com/Autocompleter-update-%28again%29-tf2234389.html#a61979
51
Sent from the JQuery forum at Nabble.com.
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
Re: [jQuery] Autocompleter update (again)
This is a Firefox bug. On 9/7/06, kain [EMAIL PROTECTED] wrote: I've tried the latest version right now, sometimes I get Errore: uncaught exception: Permesso negato per ottenere la proprietà HTMLDivElement.parentNode in my js console, that sounds like Access denied to obtain the property HTMLDivElement.parentNode btw the problem of two nested divs I explained in my previous post has disappeared. 2006/9/7, Dylan Verheul [EMAIL PROTECTED]: After all the IE transparecny issues, I decided to take a closer look at what I was doing at the DOM level, and I looked at solutions of other plugin authors. It turned out that I was using a workaround for a bug that existed in earlier versions of jQuery that had since been fixed. Also, the DatePicker plugin had a more elegant way of handling the IE transparency bug. So: - Autocomplete no longer uses a wrapper DIV - IE transparency issues seem resolved - The plugin file is smaller in size - I optimized some other stuff I tested in IE, Opera and Firefox. You will probably need to take a look at your CSS if you update to this newer version, espcially the iframe bit (see source code of my example page). I may include the iframe CSS hardcoded in a next release. http://www.dyve.net/jquery?autocomplete ( docs on the site ) ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/ -- kain kuht.it ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/ ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
Re: [jQuery] Autocompleter update (again)
On 9/7/06, Jason Huck [EMAIL PROTECTED] wrote: This looks pretty nice. Attempting to implement now, got a couple of questions: 1) Using the CSS in your demo page, what's the easiest way to nudge the entire results list down a bit? For some reason mine are popping up directly over the input element instead of just beneath it, obscuring it. This is my biggest issue right now, correct positioning of the results set. I can only say that you'll need to experiment with the CSS. I still get different results in different browsers, and even then depending on the layout (tables, liquid, etc) used. This is a completely new terrain for me, and any suggestions are welcome. The issue at hand: I have an input box. I want to position a DIV with position:absolute exactly below this input box. 2) Is there something I can add to programmatically disable the default forms-autocomplete function in browsers? FF's default menu choices are competing with the plugin's choices. I'll add this to the plugin, but you can write your input box as input ... autocomplete=off / 3) Also, a note: On my test page I have a div with overflow set to auto. The scrollbar in that div is bleeding through the autocomplete menu. Do you have a test page online? Then I can see if the problem also exists in FF/Win. ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
