bugzilla.mozilla.org will be intermittently unavailable on Saturday, March 24th, from 16:00 until 20:00 UTC.
Since 1.0 Release Candidate 1, the mode_switch key used to enter e.g. the @ and | symbols on a german keyboard (AltGr key) fails to work if the X Keyboard Extension (XKB) is disabled. More exactly, I'm using XFree86 4.1.0 with the option setting Option "XkbDisable" "True" in /etc/X11/XF86Config (because of non-Mozilla related problems with both XKB and xmodmap enabled). If this option is set to false, as it is the default setting, the AltGr / mode_switch key works, but if it is set to true, it does not. The problem did not occur in Mozilla 0.9.9 and previous versions. It seems to affect all keyboard input, but the problem is most severe in text editing fields (cannot even enter an email address).
Editor:Core is XP code, so this has to be a problem in the backend widget event code. Changing component from Editor:Core to XP Toolkit/Widgets and reassigning to default owner. Cc'ing a few linux and intl folks that might know this kind of stuff.
Assignee: kin → jaggernaut
Component: Editor: Core → XP Toolkit/Widgets
QA Contact: sujay → jrgm
Further investigation has shown the following: The problem only occurs if Mode_switch is assigned to the Mod4 modifier, "xmodmap -e 'add Mod4 = Mode_switch'". If assigned to Mod2, Mod3, or Mod5, Mozilla recognizes the key even with XKB disabled. So this is no longer a major problem for me, but still something that should be corrected, I think.
Severity: major → minor
status of this?
Gunnar, can you reproduce this problem with current versions of mozilla?
> Gunnar, can you reproduce this problem with current versions of mozilla? Yes: $ xmodmap -e 'clear mod2' $ xmodmap -e 'add Mod4 = Mode_switch' -> bug $ xmodmap -e 'clear mod4' $ xmodmap -e 'add mod2 = Mode_switch' -> works o.k. Gunnar
What is the state of this bug?
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.