42820 - numbers don't appear when typing in <input type="text"

Status: VERIFIED FIXED

(Core :: Layout: Form Controls, defect, P3)

Description

[Jonathan Baron]

When the first screen comes up after the introduction,
I don't see the numbers I type in the response box.  They
are there, because I am allowed to to on to the next screen
only if I type them, and that works, but I don't see them.

This may be related to bug 31181, which was reported fixed
and was indeed fixed, but this is the same test page I gave
for that.  (And I will remember not to move it this time.)

Note, I cannot find a place to say what build this is, but
it is the Milestone 16 build that just appeared on June 13.

Comment 1

[rods (gone)]

reassigning

Comment 2

[rubydoo123]

i can't repro this on win32 or mac using today's builds, SUjay can you repro 
this on today's linux build

Comment 3

[sujay]

I see the problem....I enter a number and click on submit button...nothing
happens...

Comment 4

[Jonathan Baron]

When I type in a number in the required response range (0-100), I
_can_ go on to the next screen.  But I just discovered something
else.  The original problem happened only when the number I typed
had one digit.  If I type 1 and then click on "Click here to go on",
I can go on, but I don't see the one.  If I type 11, then I see
_both_ 1's.  I've now tried all the digits, and they don't all
produce blanks.  The digits 4 and 5 produce _dots_!  Jon Baron

Comment 5

[rubydoo123]

so this is a linux only issue then, assigning to Kin since he is one of the 
linux folks -- Kin if this needs to be redirected, then please do so

Comment 6

[rubydoo123]

putting in pp keyword

Comment 7

[rubydoo123]

forgot to confirm the bug

Comment 8

[Jonathan Baron]

A little more information: The same thing happened when I was trying
to configure the browser.  When I typed in the url of the proxy server,
the first letter (h) did not appear until I typed the second (t).

Also, I have now tested all the keys, when they are typed first.  Most
yield blank, but, in addition to the numbers I mentioned before, the
letter m yields a colon, and U V W K M > and < yield either dots or
colons (upper case letters).  Jon

Comment 9

[kinmoz]

I'm thinking this was related to bug #41206 and bug #41406. I checked in a fix 
for those on 06/16/00. Jonathan, could you check if this is fixed in a newer 
build? The build ID is usually found in the bottom right corner of the browser 
window.

I'll also try to reproduce this bug in my Linux build.

Comment 10

[Jonathan Baron]

I just tested this on 2000061820 for Linux, and, indeed, this
bug has been fixed.  Jon Baron

Comment 11

[kinmoz]

Marking bug fixed as per Jonathan's comments.

Comment 12

[bsharma]

Updating QA contact.

Comment 13

[jerone]

Verified Build2001073003T os:Linix7.1