keyboard events and dead letters

On 20 mayo, 11:53, Thomas 'PointedEars' Lahn <PointedE... (AT) web (DOT) de>
wrote:

[snipped attribution novel]

Joaquín Zuazo wrote:
Thomas 'PointedEars' Lahn wrote:
Joaquín Zuazo wrote:
[103 quoted lines]


"Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.12) Gecko/20080129
Iceweasel/2.0.0.12 (Debian-2.0.0.12-0etch1)":

| keydown keyCode=68 (D) which=68 (D) charCode=0
keyIdentifier=undefined
| keypress keyCode=0 which=100 (d) charCode=100 (d)
keyIdentifier=undefined
| keyup keyCode=68 (D) which=68 (D) charCode=0
keyIdentifier=undefined

So probably it's a bug in the Firefox version of your Linux distribution.

I guess from your message, that you are pressing the key "d". This
works well with my distribution,
and with the same result you are posting.

The problem comes when I need to identify an "á" or an "ö". For that,
I must press two keys, one for
the accent ( the dead key ) and other for the letter itself with an
spanish keyboard, or an english international
keyboard, that provides dead letters also.

Then, only two keyup events are returned for all the keys pressed.

With windows, you get five keyboard events, and all the information
you need to identify
the key.
Thanks a lot for your help.

JoaquÃ*n Zuazo wrote:

Thomas 'PointedEars' Lahn wrote:
[snipped attribution novel]
JoaquÃ*n Zuazo wrote:
Thomas 'PointedEars' Lahn wrote:
JoaquÃ*n Zuazo wrote:
[103 quoted lines]

"Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.12) Gecko/20080129
Iceweasel/2.0.0.12 (Debian-2.0.0.12-0etch1)":

| keydown keyCode=68 (D) which=68 (D) charCode=0
keyIdentifier=undefined
| keypress keyCode=0 which=100 (d) charCode=100 (d)
keyIdentifier=undefined
| keyup keyCode=68 (D) which=68 (D) charCode=0
keyIdentifier=undefined

So probably it's a bug in the Firefox version of your Linux distribution.

I guess from your message, that you are pressing the key "d". This
works well with my distribution, and with the same result you are posting.

The problem comes when I need to identify an "á" or an "ö". For that,
I must press two keys, one for the accent ( the dead key ) and other
for the letter itself with an spanish keyboard, or an english international
keyboard, that provides dead letters also.

Sorry, I missed that this time.

Then, only two keyup events are returned for all the keys pressed.

I am afraid I have to confirm this (with only "keypress" suppressed):

keyup keyCode=0 which=0 charCode=0
keyIdentifier=undefined
ókeyup keyCode=79 (O) which=79 (O) charCode=0
keyIdentifier=undefined

With windows, you get five keyboard events, and all the information
you need to identify the key.

Yes, indeed (same character, same settings):

keydown keyCode=221 which=221 charCode=0
keyIdentifier=undefined
keyup keyCode=221 which=221 charCode=0
keyIdentifier=undefined
keydown keyCode=79 (O) which=79 (O) charCode=0
keyIdentifier=undefined
keypress keyCode=0 which=243 charCode=243
keyIdentifier=undefined
keyup keyCode=79 (O) which=79 (O) charCode=0
keyIdentifier=undefined

So ISTM for Linux you have to watch for a keyup event for a character key
immediately preceded by a keyup event where keyCode == which == 0.
Unfortunately, `charCode' is not available then, and ISTM keyCode/which
is specific to a keyboard layout. But maybe it suffices here.


PointedEars
--
Use any version of Microsoft Frontpage to create your site.
(This won't prevent people from viewing your source, but no one
will want to steal it.)
-- from <http://www.vortex-webdesign.com/help/hidesource.htm>

So ISTM for Linux you have to watch for a keyup event for a character key
immediately preceded by a keyup event where keyCode == which == 0.
Unfortunately, `charCode' is not available then, and ISTM keyCode/which
is specific to a keyboard layout. But maybe it suffices here.

The problem is than you can not know even what kind of accent was
pressed.
The only place where you can get the information is within the input
box
value.

I think this is a bug of Firefox.

JoaquÃ*n Zuazo wrote:

So ISTM for Linux you have to watch for a keyup event for a character key
immediately preceded by a keyup event where keyCode == which == 0.
Unfortunately, `charCode' is not available then, and ISTM keyCode/which
is specific to a keyboard layout. But maybe it suffices here.

The problem is than you can not know even what kind of accent was
pressed. The only place where you can get the information is within
the input box value.

Right. So that would mean evaluation after input, using .selectionStart and
..selectionEnd. Not pretty, but works.

I think this is a bug of Firefox.

Or of X? Yes, you should file a bug.


PointedEars
--
Prototype.js was written by people who don't know javascript for people
who don't know javascript. People who don't know javascript are not
the best source of advice on designing systems that use javascript.
-- Richard Cornford, cljs, <f806at$ail$1$8300dec7 (AT) news (DOT) demon.co.uk>