Closed
Bug 133776
Opened 23 years ago
Closed 23 years ago
Input/cursor out of TEXTAREA-field
Categories
(Core :: Layout: Form Controls, defect)
Tracking
()
People
(Reporter: bugzilla, Assigned: rods)
References
()
Details
Attachments
(2 files)
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.9+)
Gecko/20020326
BuildID: 2002032603
(The URL given above is a subset of www.dialing.de!)
The given TEXTAREA-field is thought to input 160 chars of text. But there is not
enough space left to really type in 160 chars. When you now reach the end of the
TEXTAREA-input-field, the cursor moves outside the field and you only see some
black rectangles directly below the input-field.
Reproducible: Always
Steps to Reproduce:
1. login to www.dialing.de (if you do not have a German providers cellular
phone, you are not able to register for that site!)
2. Click on "SMS senden"
3. Click on one of the listed phone-providers below "Deutschland:", e.g. VIAG
4. Type in 160 chars in the TEXTAREA-field "SMS Text"
Actual Results: Please take a look at
http://www.vr-web.de/~robert.hofmann/MozillaBugReports/dialing.de/form-bug.jpg
where you will see what the result on my screen is.
Expected Results: A scroll bar for the TEXTAREA-field to scroll down or a
bigger TEXTAREA-input-box.
For the source-code of the page, please visit this link:
http://www.vr-web.de/~robert.hofmann/MozillaBugReports/dialing.de/form-bug.jpg
If you are not able to use the original URL given as bug-URL above, you can use
this one. I am not sure it the bug-URL is still valid if my session times out.
Reporter | ||
Comment 1•23 years ago
|
||
Reporter | ||
Comment 2•23 years ago
|
||
Reporter | ||
Comment 3•23 years ago
|
||
I now have attached the two files I was reffering to as attachment to this bug.
Sorry for inconvenience, yesterday I was not aware of all possibilities of
bugzilla ;-)
*** This bug has been marked as a duplicate of 59018 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•