Most noticable on Aim, but you see this in Mail also. Mac 2000-02-23-12 M14 Win 2000-02-23-09 M14 Linux 2000-02-23-08 M14 Steps to reproduce (Mail): 1)Launch Seamonkey. Setup mail if you haven't already. 2)After the mail account has been setup, launch Mail via Tasks-->Mail (Be sure the "Save Password" option is *not* set for mail in Mail/News Account settings) 3)Click on the Inbox under your users folder to get the password dialog. Actual Results: Password dialog is wider than a normal field width, and is missing it's bottom and right side's border. It is also higher than a normal fields height. Steps to reproduce (in AIM): 1)Launch Seamonkey and invoke the AIM sign On Screen via Tasks-->Instant Messenger. Compare dimensions of the Password and Screen Name fields. 2)Also view the AIM sign on screen in the Buddy List Sidebar panel in Mail or the Browser. Actual results: Note the "Password" field is higher than the "Screen Name" field, and is missing it's bottom and right side's border.
reassigning to evaughan. Eric, Hyatt says you may already have fixed this...
Assignee: trudelle → evaughan
Status: NEW → ASSIGNED
Target Milestone: M14
On: Linux 2.2.14 (RedHat 6.1, custom kernel) with KDE 1.1.2 & XFree86 3.3.6 Similar bug - Password field for logging onto a HTTP site (non-SSL - Specifically a site running on Apache with Basic Authentication (i.e. 'require valid-user') turned on) that is password protected is 1.5 to 2x the size of the login-name field, but in my case, it doesn't permit the entry of a password - The mouse cursor does not change to an 'I' shape when moved over or when clicking on the field, and there is no effect from the above actions. Also, tab and other keyboard actions have no effect.
*IGNORE* - more massive spam, changing open XPToolkit bug's QA contact to email@example.com
QA Contact: paulmac → jrgm
Target Milestone: M14 → M15
Mass-moving most M15 bugs to M16
Target Milestone: M15 → M16
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.