Closed Bug 42264 Opened 24 years ago Closed 24 years ago

Unable to type values in textfield after switching Tab in tabbed dialogs

Categories

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

x86
Windows NT

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: skasinathan, Assigned: kinmoz)

References

Details

(Whiteboard: [nsbeta2+])

Steps:
1. Try to create a new AB Card. You can enter all the info under 'Name' 
titledbox. You cannot enter any other info in all other titledboxes (like 
Internet, Phones...). I'm not able to place the cursor in any of these fields.


Build and Platform: 
Windows debug build pulled around noon today.

Additional info:
But if I type something in these fields (you can't see the cursor or the text 
you type) and if I click OK, it seems to store all the information that I typed.
suresh - this may be related to a browser/ender bug?
cc: beppe.
Severity: normal → major
Keywords: nsbeta2
QA Contact: lchiang → esther
reassigning to beppe.  I'm not sure if this is an editor bug or a toolkit bug.  
To reproduce:

Open up the address book.
Click on the new card button
Try putting your cursor in various edit fields.  Only the first and last name 
will let you type in them.
Assignee: putterman → beppe
Assigning to kin@netscape.com.
Assignee: beppe → kin
Target Milestone: --- → M16
Accepting bug.
Status: NEW → ASSIGNED
Putting on [nsbeta2+] radar for beta2 fix. 
Whiteboard: [nsbeta2+]
Changing summary to reflect more general problem when using any "tabbed" dialog.
This makes it impossible to test my Table Properties dialog.
Blocks: 20973
Summary: Unable to type values in Address Book card. → Unable to type values in textfield after switching Tab in tabbed dialogs
M16 has been out for a while now, these bugs target milestones need to be 
updated.
I think evaughan had a dup of this bug that he fixed (can't find it offhand.)
It now seems to be working ok.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Charley, are you talking about bug #43206?

I see it fixed in my Linux debug build from today too.
I'm not sure if fixing 42306 fixed this as well, but I suppose it doesn't 
really matter, as long as this bug is fixed!
*** Bug 43465 has been marked as a duplicate of this bug. ***
I think fixing of 39358 fixed this.  I will test this with a build after 6/22
Using build 2000-06-23 on win98, mac and linux this is fixed.  Verified
Status: RESOLVED → VERIFIED
*** Bug 43372 has been marked as a duplicate of this bug. ***
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.