Thanks for the info. I'm using the scriptaculous Autocompleter.local
(v1.8). I made this change in controls.js and it works fine now. I
believe they are now aware of the bug and will include the fix in
their next release.
On Nov 8, 10:19 am, "Mislav Marohnić" <[EMAIL PROTECTED]>
wrote:
> Hi Ru
Really really good analysis:
http://unixpapa.com/js/key.html
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Prototype: Core" group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe
Just tested with this:
$('inputbox')
.observe('keydown', function (e) { $('debug').insert('Keydown ' +
e.keyCode + '
'); })
.observe('keyup', function (e) { $('debug').insert('Keyup ' +
e.keyCode + '
'); })
.observe('keypress', function (e)
Oh, tested in IE7 and FF2.
If i type really fast, then I found that I had multiple kd-kp events
followed by several ku events, but the kd always prefixed the kp event.
Not sure about opera/safari.
IE7 had charCode in kp keyCode and FF had 0.
The quirks mode article might help.
Gareth
On Nov 9, 20
On Nov 9, 2007 1:11 AM, Gareth Evans <[EMAIL PROTECTED]> wrote:
> Mislav,
>
> Looking forward, would observing the keydown event *as well* as the
> keypress event when the keypress event is observed and copying the keycode
> property to the keypress event object be an option?
For those who need
Mislav,
Looking forward, would observing the keydown event *as well* as the keypress
event when the keypress event is observed and copying the keycode property
to the keypress event object be an option?
Gareth Evans
On Nov 9, 2007 4:19 AM, Mislav Marohnić <[EMAIL PROTECTED]> wrote:
> Hi Russel
Hi Russel,
In Prototype 1.6 we no longer translate "keypress" to "keydown":
http://dev.rubyonrails.org/changeset/7928
We did that before because the codes are not properly set cross-browser with
that event. This is exactly what you're having issues with now, in my
opinion. I suggest you use "keyu
