Closed Bug 159733 Opened 22 years ago Closed 20 years ago

the comma on the numeric keyboard doesn't work

Categories

(SeaMonkey :: UI Design, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 108170

People

(Reporter: stefan.brandner, Assigned: samir_bugzilla)

References

Details

When I activate the numbers at the numeric keypad the comma doesn't work.
Instead I get the pipe symbol '|'.
I don't think it is language dependent because I tried it with two
different laguages and the problem appears on both.

I heard it doesn't happen with the windows version.
Testing with a current CVS build, Linux, i get a periode, not a comma.
The comma is accessed by pressing shift+Del (or NumLock first, then del.)
Norwegian Keyboard layout. Works fine otherwise.

Bug as i see it has nothing to do with mailnews though: it can be seen in all
applications i use - not only mozilla.

Reporter: Can you confirm that your other applications show the comma comma
correct (and not a |) when you use the numeric keypad?
reassign to xpapp
Assignee: ducarroz → sgehani
Component: Composition → XP Apps
Product: MailNews → Browser
QA Contact: esther → paw
I have KDE 3.0.2 installed and the comma works for all KDE programs as well as Open Office.  Mozilla is the only program which shows this behaviour.  
Stefan, are you still experiencing this problem? Can you reproduce it with a
current copy of mozilla?

What locale is your system configured to use?
I was able to fix the problem by changing ~/.Xmodmap

I added following line:

keycode 91 = KP_Delete comma

Now the comma works!

Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
*** Bug 200262 has been marked as a duplicate of this bug. ***
BTW: I believe that this bug was resolved incorrectly.  Either it has nothing to
do with Mozilla and should have been marked INVALID, or there actually is a
Mozilla problem and it should have remained open so that it could be properly
fixed (rather than resorting to workarounds).  I suspect that INVALID is more
appropriate, but am not certain.
This bug is very much alive in Linux.
I have reproduced the | instead of , on 3 Linux computers. It applies to Firefox
0.8 and T-bird 0.5

I have also reproduced the bug in the latest nightly Firefox for Linux.
All other applications on all 3 computers render the comma correctly, except for
the Mozillas.
reopening bug, awaiting more information from affected users
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.6) Gecko/20040207 Firefox/0.8 - bug
still exists
Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.6) Gecko/20040115 - bug disappeared

both tested under Kernel 2.4.22

Changing of /etc/X11/Xmodmap had no effect
Jochen, could you please test this with a recent nighty and/or 1.7RC2/1.8a1?
1.6 is a little old to be of any use here...
(In reply to comment #11)
Today I downloaded the latest Firefox nightly and the problem persists.

Here I type "1/2" with decimal comma: 0|5

All other applications are fine. (Mandrake 10, KDE, 2.6-kernel)
This bug is still bugging me! ;) Running Firefox 0.9 RC1 on Mandrake Linux 10
with KDE 3.2 and a German keyboard. Only the comma on the num pad is not
working, every other key works correctly. Only on Linux, no problems in Windows.

This is the output i get from my numeric pad:
/*-
789+
456
123
0|

It SHOULD be:
/*-
789+
456
123
0,


might this be related to KDE perhaps?

Could somebody in a GNOME enviroment please check this bug with a recent nighty
of both Firefox and the Mozilla suite and report back?
Thanks.
Mozilla should use "," instead of "|" as separator char. This happens when
KP_Separator is pressed.

Please fix this now that you know the cause!

My versions:

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510
Gnome 2.6.0

*** This bug has been marked as a duplicate of 108170 ***
Status: NEW → RESOLVED
Closed: 21 years ago20 years ago
Resolution: --- → DUPLICATE
Product: Core → Mozilla Application Suite
You need to log in before you can comment on or make changes to this bug.