Closed (outdated)
Project:
Drupal core
Version:
7.x-dev
Component:
javascript
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
28 May 2010 at 21:53 UTC
Updated:
14 May 2015 at 13:13 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
yesct commentedIn preparation for the new "major" issue priority, I'm tagging this (not actually critical, but still important) issue as priority-major.
See: http://drupal.org/node/669048#comment-3019824 (#669048: We should have four priorities not three (introduce a new 'major' priority)) for more information about the coming major issue priority.
Comment #3
catchThis is just a normal bug, not critical.
I wasn't able to reproduce this bug with uim/anthy/hiragana when trying to test the patch - could you post steps to reproduce?
Comment #4
droplet commented1. install Japanese IME (Microsoft IME), Chinese New ChangJie (any NEW xxx)
2. typing...
Screen Capture:
http://www.youtube.com/watch?v=-zv-UBc1Puw
Comment #5
catchEr, no. You have to have tags in the db matching the ime input, which I'd stupidly missed, but no need to get sarky. Managed to reproduce with both kanji and romaji input, however applying the patch didn't fix it for me on ubuntu with chrome + uim/anthy.
Comment #6
droplet commenteddamn.
ubuntu with Chrome + uim only trigger keydown
http://jsbin.com/uyequ3
Comment #7
casey commentedIs that text event triggered by the ime? It is not part of any standard, or is it?
Comment #8
marcingy commentedChanging to major as per tag.
Comment #9
mustanggb commentedTag update
Comment #10
yaoweizhen commentedIt works with drupal-6.
Comment #11
droplet commented@casey, @yaoweizhen
not sure how the IME works.
Seems diff OS platform and IME have inconsistent behavior.
setInterval maybe the only way to solve this problem but not the best way.
above patch working for most Windows OS that cover 80%~95% IME users.
Can we apply the patch first and seek a best way later ??
Comment #12
casey commentedDoesn't keydown, keyup or keypress give consistent results? text event is not part of any standard to my knowledge, so I rather don't use it. If we do, we need at least a reference link where it is documented.
Comment #13
sun.core commentedThis is a normal feature request.
Should use
.bind('keyup.autocomplete change.autocomplete', ac.onkeyup)
...at least. Probably needs a event stack protection in ac.onkeyup() then though.
Powered by Dreditor.
Comment #14
catch#1070208: taxonomy autocomplete doesn't support Chinese input was duplicate.
This is at least a bug, you can't type Japanese without an IME, which means you can't use autocomplete without one (maybe you could copy and paste from a text editor, but that's not really 'autocomplete').
Comment #15
droplet commentedUntil now I don't see any perfect way to fix all OS users. but it's patch could cover most IME users. bump up version. Will be back with a new patch this week.
Comment #16
nod_Any news on the patch?
Also can you test the jquery ui autocomplete and see if it works better?
Comment #17
droplet commented"jquery ui autocomplete": Nope.
use HTML5 oninput event, it may not work in old firefox.
Comment #18
nod_Aw :/ we'll have to fill a bug to jquery ui too then.
Comment #19
droplet commentedNever know CORE is using UI 1.9-PRE. Just tested #675446: Use jQuery UI Autocomplete and found it works well.
Looking into soruce, 1.9 catches INPUT events too.
We may need somebody test it on Linux
Comment #20
jimyhuang commented#17 patch fix firefox search problem. Now have popup result when typing after patched.
But still have problem when ie and firefox user press "enter" to bring ime text to textfield, but popup will trigged when this "enter" also trigger js keycode "13" event. I suppose write some exception for ie / firefox to prevent hidePopup() triggered in keyup event.
Comment #21
jimyhuang commentedUpdate: For user who have problem on firefox / ie enter triggered described at #20 , attachment may solve your problem.
Comment #24
droplet commentedComment #25
nod_Should be fixed by the move to jquery ui. If not feel free to reopen.
Comment #26
droplet commented