Closed
Bug 79435
Opened 24 years ago
Closed 23 years ago
INPUT not displaying text as typed
Categories
(Core :: Layout, defect)
Core
Layout
Tracking
()
People
(Reporter: dv5a, Assigned: karnaze)
References
Details
Attachments
(5 files)
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9+) Gecko/20010507
BuildID: 2001050720
Input fields (type=text), sometimes do not display characters while typing. I
found this behaviour in USA.net while having Monospace font preference set to
"Lucida Console"
Reproducible: Always
Steps to Reproduce:
1. Set your monospace font preference to "Lucida Console"
2. Go to http://www.netaddress.com/
3. Write some text in "Login Name" field
Actual Results: Some characters are not displayed while typing
Expected Results: Characters should display after any keypress
It seems that 1st character appears, 2nd. does not. 3rd, displays correctly,
4th. does not, and so on.
|
Reporter | |
Comment 1•24 years ago
|
||
|
||
Comment 2•24 years ago
|
||
I see this also with Linux build 2001-05-07-08 (I do have the Lucida Console font).
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows NT → All
Hardware: PC → All
|
|
Reporter | |
Comment 3•24 years ago
|
||
|
|
Reporter | |
Comment 4•24 years ago
|
||
"Lucida Console" font seems not to be necessary to trigger this problem.
I switched back to "Courier New" Font and was able to reproduce this behaviour.
So, I did a more simplified testcase. ( attachment 33537 [details] )
Sorry for the spam.
|
||
Comment 5•24 years ago
|
||
I see this also (Mac)
|
|
||
Comment 7•24 years ago
|
||
I'm not sure this is our bug but I will attach a minimal testcase. It seems
that the table is required and the contents of the cell must wrap before the
input field in order to see this bug.
|
|
||
Comment 8•24 years ago
|
||
|
||
Comment 9•24 years ago
|
||
looking at the second testcase, I noted that it had a couple coding errors. I
moved the form element start and end tags to be within the TD and not between
the table and tr. I also included the action and method attributes to the form
elements and I included a doctype statement so I could parse the document at:
http://validator.w3.org/file-upload.html
I redid the testcase to include 3 input elements, the first one is nested within
the span. The second one is nested within a div. The third is a standalone input
element. The text input worked fine for #2 and #3, but does not work fine for
the one nested in a span element.
|
|
||
Comment 10•24 years ago
|
||
|
|
Reporter | |
Comment 11•24 years ago
|
||
The problem also occurs with <font></font> tags or even an invalid tag (e.g.
<xxx></xxx>)
|
|
||
Comment 12•24 years ago
|
||
if it happens in a sequence where it is illegal nesting or invalid nesting then
that is most likely a won't fix. However, for it to not work with elements such
as span and font is an issue. I will continue to test this with nested elements
inside tables, and with the same element structure outside of tables to see if
maybe that is where the problem originates.
|
|
||
Comment 13•24 years ago
|
||
I tested this by submitting to a server and found that the data is indeed there,
it just isn't rendering (probably a reflow issue). In the first input field, I
typed in ff, the first f rendered, the second f did not. The HTTP server
feedback was this:
HTTP Request Header:
GET /foo.html?spanme=ff&divme=&plainme= HTTP/1.1
handing over to layout
Assignee: beppe → karnaze
Component: HTML Form Controls → Layout
QA Contact: vladimire → petersen
|
||
Comment 14•24 years ago
|
||
|
|
||
Comment 15•24 years ago
|
||
I just attatched the minimal test case to reproduce this bug. I intentionally
removed all the whitespace between the <body> and </body> tags to reduce the
noise in the content tree.
To see the bug, the textfield must be in a table, beneath an inline node, and it
must wrap to the 2nd line in the table cell.
|
||
Comment 16•24 years ago
|
||
*** Bug 86377 has been marked as a duplicate of this bug. ***
|
|
Reporter | |
Comment 17•24 years ago
|
||
After many years, NetAddress has changed the layout of its home page and now it
works fine. So I'm removing the URL.
Nevertheless, the bug is still valid.
|
|
||
Comment 18•24 years ago
|
||
*** Bug 94987 has been marked as a duplicate of this bug. ***
|
||
Comment 19•23 years ago
|
||
WORKSFORME.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
|
|
||
Comment 20•23 years ago
|
||
Actually this is still a problem, and is a dup of bug 91423.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
|
|
||
Comment 21•23 years ago
|
||
*** This bug has been marked as a duplicate of 91423 ***
Status: REOPENED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → DUPLICATE
|
|
Reporter | |
Comment 22•23 years ago
|
||
You need to log in
before you can comment on or make changes to this bug.
Description
•