Last 30 days

• Dec 06, 2009

  Main Wiki page commented on by hke...@126.com   -   I hava a problem.when I want to use ajax_get.I can not get the result from server. My code as follow: <? $param = $_REQUEST['q']; $status = array( "text"=>"hello", "value"=>"myname" ); $result = json_encode($status); echo $result; ?> echo json-object But my client can not accept the result.who can help me?thanks

  I hava a problem.when I want to use ajax_get.I can not get the result from server. My code as follow: <? $param = $_REQUEST['q']; $status = array( "text"=>"hello", "value"=>"myname" ); $result = json_encode($status); echo $result; ?> echo json-object But my client can not accept the result.who can help me?thanks
• Dec 04, 2009

  Main Wiki page commented on by LightingMan112   -   I found a problem while using IE in mult mode. if you click the alternative option,it will overwritten the first value

  I found a problem while using IE in mult mode. if you click the alternative option,it will overwritten the first value

Earlier this year

• Oct 16, 2009

  issue 2 (problem witch const and jsondata) commented on by craigdcalef   -   I had this same problem. It's caused by using "get" instead of "ajax_get" Change the line that says $('#msgto').autocomplete({ get:sugg,cache:false,multi:multi}); TO $('#msgto').autocomplete({ ajax_get:sugg,cache:false,multi:multi}); And that should solve at least THAT problem for you.

  I had this same problem. It's caused by using "get" instead of "ajax_get" Change the line that says $('#msgto').autocomplete({ get:sugg,cache:false,multi:multi}); TO $('#msgto').autocomplete({ ajax_get:sugg,cache:false,multi:multi}); And that should solve at least THAT problem for you.
• Oct 04, 2009

  issue 12 (No result all the time) reported by khangdm.ec   -   What steps will reproduce the problem? 1. Type word 2. No result I think the reason is there's no dict to look up words on my server. So in this case what should I do?

  What steps will reproduce the problem? 1. Type word 2. No result I think the reason is there's no dict to look up words on my server. So in this case what should I do?
• Aug 28, 2009

  issue 11 (jquery autocomplete is not compatible with other JS librarie...) reported by use...@laliluna.de   -   The reason is that at the end of the file $ is passed. In compatible mode $ may be something else than jQuery. })($); Just replace it with the following code })(jQuery);

  The reason is that at the end of the file $ is passed. In compatible mode $ may be something else than jQuery. })($); Just replace it with the following code })(jQuery);
• Jul 27, 2009

  issue 9 (Access to search input in callback function) commented on by drgisc   -   Also http://code.google.com/p/jqac/issues/detail?id=6

  Also http://code.google.com/p/jqac/issues/detail?id=6
• Jul 27, 2009

  issue 10 (Arrow keys don't work on IE8) commented on by drgisc   -   http://code.google.com/p/jqac/issues/detail?id=1 is a fix.

  http://code.google.com/p/jqac/issues/detail?id=1 is a fix.
• Jul 27, 2009

  issue 10 (Arrow keys don't work on IE8) reported by drgisc   -   Keys ArrowUP and ArrowDOWN don't work on IE8 (jqac version: 1.4.2) - you can't move through elements with keyboard (enter still works).

  Keys ArrowUP and ArrowDOWN don't work on IE8 (jqac version: 1.4.2) - you can't move through elements with keyboard (enter still works).
• Jul 27, 2009

  issue 9 (Access to search input in callback function) reported by drgisc   -   I needed an access to search input in a callback function, so the fasted way to do that was for me a little change in the script (line 405): from: options.callback( suggestions[current_highlight-1] ); to: options.callback( suggestions[current_highlight-1], me ); and after then callback function takes two parameters, and one can do something like: function userCallback(v, me) { var id = $(me).attr('id'); //[...] } Or is there another way to access search input, perhaps?

  I needed an access to search input in a callback function, so the fasted way to do that was for me a little change in the script (line 405): from: options.callback( suggestions[current_highlight-1] ); to: options.callback( suggestions[current_highlight-1], me ); and after then callback function takes two parameters, and one can do something like: function userCallback(v, me) { var id = $(me).attr('id'); //[...] } Or is there another way to access search input, perhaps?
• Jul 21, 2009

  issue 8 (Suggestions don't clear on blur) commented on by mario.estrada   -   My suggestion inserted a bug in the code where if you click on a suggestion it won't be selected, a fix for this would be to use the funcion 'setHighlightedValue' instead of 'clearSuggestions', like this: // clear on blur me.blur(function() { setHighlightedValue(); });

  My suggestion inserted a bug in the code where if you click on a suggestion it won't be selected, a fix for this would be to use the funcion 'setHighlightedValue' instead of 'clearSuggestions', like this: // clear on blur me.blur(function() { setHighlightedValue(); });
• Jul 17, 2009

  issue 8 (Suggestions don't clear on blur) reported by mario.estrada   -   What steps will reproduce the problem? 1. Write something on the autocomplete field 2. Write something that doesn't get suggested 3. Change focus to other input What is the expected output? What do you see instead? Suggestions should be cleared. What version of the product are you using? On what operating system? Latest Please provide any additional information below. To fix just add these lines at 179: // clear on blur me.blur(function() { clearSuggestions(); });

  What steps will reproduce the problem? 1. Write something on the autocomplete field 2. Write something that doesn't get suggested 3. Change focus to other input What is the expected output? What do you see instead? Suggestions should be cleared. What version of the product are you using? On what operating system? Latest Please provide any additional information below. To fix just add these lines at 179: // clear on blur me.blur(function() { clearSuggestions(); });
• Jul 09, 2009

  issue 7 (Escape + character needed) reported by koki.eml   -   What steps will reproduce the problem? 1. use it to look up a value like '+43.218' (telefone number) 2. 3. What is the expected output? What do you see instead? regex match result What version of the product are you using? On what operating system? linux / firefox / debian testing Please provide any additional information below. i have attached a patch Thank You for this plugin! All the best, klaus

  What steps will reproduce the problem? 1. use it to look up a value like '+43.218' (telefone number) 2. 3. What is the expected output? What do you see instead? regex match result What version of the product are you using? On what operating system? linux / firefox / debian testing Please provide any additional information below. i have attached a patch Thank You for this plugin! All the best, klaus
• Mar 06, 2009

  issue 6 (On callback, also pass through the autocomplete'd element) reported by mark.mandel   -   This is a small enhancement. I added to setHighlightedValue(), an extra argument to the callback: options.callback( suggestions[current_highlight-1], me ); This gives me access to the original item, and allows me to do some things more dynamically, based on values stored on the element I'm applying autocomplete on. Nice work on this plugin, it's been a real time saver.

  This is a small enhancement. I added to setHighlightedValue(), an extra argument to the callback: options.callback( suggestions[current_highlight-1], me ); This gives me access to the original item, and allows me to do some things more dynamically, based on values stored on the element I'm applying autocomplete on. Nice work on this plugin, it's been a real time saver.
• Feb 10, 2009

  issue 5 (No option to disable inserting the highlighted selection int...) commented on by giorgio.seregni   -   ddd

  ddd
• Feb 10, 2009

  issue 5 (No option to disable inserting the highlighted selection int...) commented on by giorgio.seregni   -   ee

  ee
• Jan 29, 2009

  issue 5 (No option to disable inserting the highlighted selection int...) reported by peterkaufmanenator   -   There's no option to disable inserting the highlighted option from the selection list into the input box upon pressing the return key. In some locales where IME input modes are used, this behavior can wreak havoc when the user is trying to type in text. This is because when typing in CJK characters, users have to use the return key to select which characters get inputted. As a result, when trying to select characters to go into the input field, the autocomplete goes off and inserts the first choice from the suggestions menu even though the user hasn't actually selected anything from the suggestions menu yet. I think there should be an option such that when the return key is pressed, the autcompleter does nothing and the event bubbles up as normal. I don't think it's a huge change--if you'd like me to, I'm happy to submit a patch to you.

  There's no option to disable inserting the highlighted option from the selection list into the input box upon pressing the return key. In some locales where IME input modes are used, this behavior can wreak havoc when the user is trying to type in text. This is because when typing in CJK characters, users have to use the return key to select which characters get inputted. As a result, when trying to select characters to go into the input field, the autocomplete goes off and inserts the first choice from the suggestions menu even though the user hasn't actually selected anything from the suggestions menu yet. I think there should be an option such that when the return key is pressed, the autcompleter does nothing and the event bubbles up as normal. I don't think it's a huge change--if you'd like me to, I'm happy to submit a patch to you.

Older

• Dec 17, 2008

  issue 1 (Down Up arrow keys doesn't work in IE7 & Safari 3.1.1 (windo...) commented on by crysfel   -   thanks!! it works like a charm :d

  thanks!! it works like a charm :d
• Dec 04, 2008

  issue 4 (Small mistake in default css file) Status changed by clonyara   -  

  Status: Accepted

  Status: Accepted
• Oct 07, 2008

  issue 4 (Small mistake in default css file) reported by rzajac   -   In css file last css rule starts like this: .jqac-menu .jqs-info { ...} It should be: .jqac-menu .jqac-info { ...}

  In css file last css rule starts like this: .jqac-menu .jqs-info { ...} It should be: .jqac-menu .jqac-info { ...}
• Sep 19, 2008

  issue 3 (ENTER key doesn't work for the field even if suggestions are...) commented on by pakonet   -   I forgot to mention, I'm using Firefox 3 with the 1.4.2 version of the plugin and the newest version of jQuery. As a quick fix, I changed: me.keypress(function(ev){ // ev.which doesn't work here - it always returns 0 switch(ev.keyCode){ case RETURN: case ESC: return false; to: me.keypress(function(ev){ // ev.which doesn't work here - it always returns 0 switch(ev.keyCode){ case RETURN: case ESC: return !suggestions_menu; in the plugin code, and now the ENTER key seems to work fine. Maybe you should consider including this fix in the new version of the plugin, if it doesn't break anything.

  I forgot to mention, I'm using Firefox 3 with the 1.4.2 version of the plugin and the newest version of jQuery. As a quick fix, I changed: me.keypress(function(ev){ // ev.which doesn't work here - it always returns 0 switch(ev.keyCode){ case RETURN: case ESC: return false; to: me.keypress(function(ev){ // ev.which doesn't work here - it always returns 0 switch(ev.keyCode){ case RETURN: case ESC: return !suggestions_menu; in the plugin code, and now the ENTER key seems to work fine. Maybe you should consider including this fix in the new version of the plugin, if it doesn't break anything.
• Sep 19, 2008

  issue 3 (ENTER key doesn't work for the field even if suggestions are...) commented on by pakonet   -   I forgot to mention, I'm using Firefox 3 with the 1.4.2 version of the plugin and the newest version of jQuery. As a quick fix, I changed: // ev.which doesn't work here - it always returns 0 switch(ev.keyCode){ case RETURN: case ESC: return false; to: // ev.which doesn't work here - it always returns 0 switch(ev.keyCode){ case RETURN: case ESC: return !suggestions_menu; in the plugin code, and now the ENTER key seems to work fine. Maybe you should consider including this fix in the new version of the plugin, if it doesn't break anything.

  I forgot to mention, I'm using Firefox 3 with the 1.4.2 version of the plugin and the newest version of jQuery. As a quick fix, I changed: // ev.which doesn't work here - it always returns 0 switch(ev.keyCode){ case RETURN: case ESC: return false; to: // ev.which doesn't work here - it always returns 0 switch(ev.keyCode){ case RETURN: case ESC: return !suggestions_menu; in the plugin code, and now the ENTER key seems to work fine. Maybe you should consider including this fix in the new version of the plugin, if it doesn't break anything.
• Sep 19, 2008

  issue 3 (ENTER key doesn't work for the field even if suggestions are...) commented on by pakonet   -   I forgot to mention, I'm using Firefox 3 with the 1.4.2 version of the plugin and the newest version of jQuery.

  I forgot to mention, I'm using Firefox 3 with the 1.4.2 version of the plugin and the newest version of jQuery.
• Sep 19, 2008

  issue 3 (ENTER key doesn't work for the field even if suggestions are...) reported by pakonet   -   The ENTER key doesn't work for the input field when I add the autocomplete feature. Pressing ENTER is blocked even if the suggestions aren't displayed - the form doesn't get submitted.

  The ENTER key doesn't work for the input field when I add the autocomplete feature. Pressing ENTER is blocked even if the suggestions aren't displayed - the form doesn't get submitted.
• Aug 23, 2008

  issue 2 (problem witch const and jsondata) reported by andrzejborkowski   -   What steps will reproduce the problem? js: function sugg(key,cont){ var res=[]; $.get('<?php echo $html->base; ?>/messages/autocomplete/',{q:key}, function(data){ $.each(data,function(i,field){ res.push({id:i, value:field}); }); cont(res); },'json'); } ...dom ready $('#msgto').autocomplete({ get:sugg,cache:false,multi:multi}); //request && rensponse {"1":"admin (Administrator)","11":"manager (Manager)","29":"general (Administrator)","30":"testing (Administrator )"} errors ! jsondata is undefined [Break on this error] for(var i=0;i<jsondata.length;i++){ jquery.a...-1.4.2.js (linia 69) cont is not a function [Break on this error] cont(res); What is the expected output? What do you see instead? What version of the product are you using? On what operating system? 1.2.6jq plugin autocomplete 1.2.4 1.2

  What steps will reproduce the problem? js: function sugg(key,cont){ var res=[]; $.get('<?php echo $html->base; ?>/messages/autocomplete/',{q:key}, function(data){ $.each(data,function(i,field){ res.push({id:i, value:field}); }); cont(res); },'json'); } ...dom ready $('#msgto').autocomplete({ get:sugg,cache:false,multi:multi}); //request && rensponse {"1":"admin (Administrator)","11":"manager (Manager)","29":"general (Administrator)","30":"testing (Administrator )"} errors ! jsondata is undefined [Break on this error] for(var i=0;i<jsondata.length;i++){ jquery.a...-1.4.2.js (linia 69) cont is not a function [Break on this error] cont(res); What is the expected output? What do you see instead? What version of the product are you using? On what operating system? 1.2.6jq plugin autocomplete 1.2.4 1.2
• Jul 29, 2008

  issue 1 (Down Up arrow keys doesn't work in IE7 & Safari 3.1.1 (windo...) reported by maqdev   -   Steps to reproduce: 1. Open http://www.cs.bgu.ac.il/~ygleyzer/files/utils/jqac/jqac_example.html with IE7 2. Enter some text and wait while autocomplete window pops up 3. Press down, up keys Expected: changing selected item when using arrow keys. Instead: Could not select item from keyboard It's desn't work in IE 7 & Safari, works correctly in Firefox 3. This problem appeared because of keypress event being used for handling keyboard messages. But arrow keys can't be handled using keypress, only by keydown/keyup. Check uploaded fixed version of plugin.

  Steps to reproduce: 1. Open http://www.cs.bgu.ac.il/~ygleyzer/files/utils/jqac/jqac_example.html with IE7 2. Enter some text and wait while autocomplete window pops up 3. Press down, up keys Expected: changing selected item when using arrow keys. Instead: Could not select item from keyboard It's desn't work in IE 7 & Safari, works correctly in Firefox 3. This problem appeared because of keypress event being used for handling keyboard messages. But arrow keys can't be handled using keypress, only by keydown/keyup. Check uploaded fixed version of plugin.