Closed Bug 125840 Opened 24 years ago Closed 24 years ago

Cannot input into Address Book fields when multiple keyboards are installed

Categories

(SeaMonkey :: MailNews: Address Book & Contacts, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 125065

People

(Reporter: momoi, Assigned: racham)

Details

** Observed with 2002-02-15 Win32 trunk build ** About the title, I am not so sure about "under the multiple keyboards .." part but I suspect users with a single keyboard are not affected. That is the only reason I can think of why this problem has not been fixed for some time. I use Windows 2000 US version with the default locale set to Japanese and I installed some 15 keyboards from the install CD. The keyboards include Japanese, Korean, 2 Chinese ones, English, French, German, etc. Here's a typical problem: 1. Have either EN or Japanese keyboard selected. 2. Open the Address Book and choose Add New Card button. 3. Try to input into any of the fields on the first page of the Address Book. I can't because I cannot insert the curson into any of the fields. 4. Now switch the keyboard to JP or EN whichever it is not set to currently. You will notice that the fields are suddenly capable of taking input. Another way in which the problem crops up. 1. Read a mail message. 2. Select the sender name & address in the view pane and right-click on the mouse to bring up the context menu. Choose "Add to Address Book" menu. 3. This bring up the Address Book with Display name and e-mail address fields filled in already -- usually. 4. However, you cannot input into any other fields. 5. Again the workaround is to switch the keyboard from the current one to something else.
Keywords: nsbeta1
A dup of bug 125065?
This problem also occurs with one keyboard. *** This bug has been marked as a duplicate of 125065 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Verified duplicate.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.