| Summary | Autocompletion incomplete with Hangul. (firefox) |
| Queue | IMP |
| Queue Version | 6.2.10 |
| Type | Enhancement |
| State | Rejected |
| Priority | 1. Low |
| Owners | |
| Requester | dgkim (at) dgkim (dot) net |
| Created | 10/22/15 (3890 days ago) |
| Due | |
| Updated | 2/14/16 (3775 days ago) |
| Assigned | |
| Resolved | 2/11/16 (3778 days ago) |
| Milestone | |
| Patch | No |
And when I comment out the following code.
//new PeriodicalExecuter(this.inputWatcher.bind(this), 0.25);
near line 94.
It seems problem solved.
Does this code can affect input element's value?
In both firefox and safari, same problem.
Which file do I need look at? regarding key stroke.
Priority ⇒ 1. Low
State ⇒ Feedback
system to let me enter Hangul characters.
Since you mentioned it depends on the browser, I tend to consider this
a browser bug intead.
Priority ⇒ 2. Medium
Type ⇒ Enhancement
Summary ⇒ Autocompletion incomplete with Hangul. (firefox)
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
State ⇒ New
Address auto-completer doesn't work properly.
In Korean, 'Hangul' character requires more than one keystroke.
For example, '???' is consist of 'rlaejrrhs',
and auto-completer starts at 'rlaejrrh', so searching is incorrect.
In the past, I made a change on file 'prettyautocomplete.js' as follows.
CODE BEGIN
ac = new Ajax.Autocompleter(this.input, this.p.uri, p_clone);
ac.opts.frequency = 1.0;
CODE END
ac.opts.frequency did the trick.
But it doesn't work any more. I think Firefox might updated some functionalty.
Today auto-completer doesn't even work properly,
And also while stroke-in a key, the cursor moves out of the character.
It means. I want to type-in '?', the result is '???'.
Of course, there is no problem with Hangul. only in address auto completion.
I mostly uses Firefox as a primary browser.
And today I tested on Chrome, there is no problem without modificaton
on prettyautocomplete.js