Closed
Bug 59960
Opened 24 years ago
Closed 24 years ago
When trying to enter information into a form, you cannot see the cursor.
Categories
(Core :: Layout: Form Controls, defect, P3)
Tracking
()
People
(Reporter: eyitope, Assigned: rods)
References
()
Details
From Bugzilla Helper: User-Agent: Mozilla/4.6 [en] (WinNT; U) BuildID: M18 Normally when trying to enter information into a form, the cursor blinks and indicates you can start typing. In Mozilla, you dont see the cursor inside the form and you are not aware that you can start typing. This occured on the www.ibm.com page, when trying to peform a search inside the search box (top left corner of page). Reproducible: Always Steps to Reproduce: 1.Go to www.ibm.com 2.Click inside the search box located on the upper left corner of the page. 3. Actual Results: After clicking inside the box, no cursor shows. Expected Results: You expect a cursor to blink inside the box, which will indicate you can start typing. Os/2 4.0 Warp; 200Mhz, Build M18
Comment 1•24 years ago
|
||
reporter: I think I can see what you are saying in windows98 but this may not be a bug. The "text" cursor is there, it is just right up against the left side of the text input (no left-padding). There are more problems with the styling of the text input though. Notice the quotes around the style colors, etc. Mozilla does a good job ignoring them, while IE, of course, renders everything even though it is wrong. Reporter do you ever see the text cursor while typing? Or is the problem more because by default, mozilla places the cursor position right up against the left side of the text input?
URL: www.ibm.com → http://www.ibm.com
Comment 2•24 years ago
|
||
This looks like a dupe of an OS/2 only defect we already have: http://bugzilla.mozilla.org/show_bug.cgi?id=56853 On OS/2, we are drawing entry field borders two big and they are overlaying the initial cursor. *** This bug has been marked as a duplicate of 56853 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•