Closed Bug 22307 Opened 26 years ago Closed 26 years ago

Cannot see Address Book Entries because the display field is too narrow

Categories

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

x86
Other
defect

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: momoi, Assigned: hangas)

Details

** Observed with 12/21/99 Win32 m12 build ** This is a regression from 12/20/99 Win32 M12 candidate build. The address book field is too narrow in this build and I cannot see the Display name, e-mail address, etc. all at once. It was working on the candidate from yesterday. Surely someone has noticed this by now, Hopefully it is being worked on.
The Build ID is: 1999122023
QA Contact: lchiang → esther
Hmm, Kat, I don't have a problem with today's M12 candidate builds 1999122023 on Win32. 1) Address Book 2) Select an address book / address card. 3) Looks fine in the display pane. 4) Edit the address book card 5) Able to see all the characters in the fields. Did you do an install with seamonkey.exe? If you do this, and M13 is in the current build directory, I believe the installer will grab the M13 builds then. (How to confirm: go into the thread pane of the mail window and delete a message. Does the msg get removed from the thread pane? If yes, then you're using M12. If no, then you're using M13)
I don't have any problem either except the very annoying one with the input (when focus jumps while entering non-ascii chars)
Lisa, I installed this build last night when it just came out. I just did an installation on another machine, and there it works OK. So, I'm going to re-install on my main machine and if it works there, then this would be an instllation error. (Hope that all that is.)
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → WORKSFORME
I re-installed on Win98-J and now it works OK. Apparently this was an installation glitch from last night. Marking it Worksforme.
Status: RESOLVED → VERIFIED
Verified also.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.