Closed Bug 102174 Opened 23 years ago Closed 23 years ago

Cannot fill in forms

Categories

(Core :: DOM: Editor, defect)

Product:
Core
Component:
DOM: Editor
Platform:
x86
Windows ME
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED DUPLICATE of bug 100130

People

(Reporter: bclinger, Assigned: kinmoz)

References

(
URL
)

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:0.9.4+) Gecko/20010927
BuildID:    2001092803

This is a previous documented bug, though I cannot find it. When a form is
presented, just as the ones with this site, information cannot be entered into
the form. I had to delete this build and install a build from yesterday to get
it rolling again.

Reproducible: Always
Steps to Reproduce:
1. Go to http://bugzilla.mozilla.org/show_bug.cgi?id=101205
2. Try to fill out the form and gosh, no go. Exit and restart the browser
   produced the same results.
3. 

Actual Results:  Cannot fill out forms.

Expected Results:  Able to fill out forms.

This is an old bug.
editor: core, or html forms? this does not belong in xp apps...

was the failure in filing out textfields, or with other form controls, or when
submitting the form...?
Assignee: pchen → kin
Component: XP Apps → Editor: Core
QA Contact: sairuh → sujay
Hmmmm I'm not having any problems filling out forms with my 09/28/01 Mozilla
debug build.
WFM in 9/28 branch build on windows.
wfm too
Click on the field and was unable to type data into the form. Tried this a
couple of times, rebooted and tried again. I deleted the build, redownloaded it,
reinstalled it, and now it is working. No changes in the installation the first
or second time - it just decided to work. Again, this is not a new bug.
With build number 2001092803 - I was able to file in this form with no problem.
I closed and reopened the window, and it would not let me. I again closed the
window and reopened it and this time it let me enter the data in this field. Wow!
With build number 2001092908 - I opened the browser went to a bug page and
attempted to add "additional comments." It would not let me. A couple of key
strokes ensued and it opened up the "save bookmarks" function - which ain't what
is suppose to happen. I then closed the browser and from the mail function,
clicked on a link to return me here, and it worked just great. Love these
problems. Ben
Just exited the program and restarted it, and it's working fine now.
duping to the more active bug

*** This bug has been marked as a duplicate of 102176 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
yo, verified.
Status: RESOLVED → VERIFIED
I've confirmed it again - exit the browser and open it again, it'll let ya fill
in the form.
The same problem exists with 2001100103 - after installing and during the
initial test, went here to see if I could enter text in any of the form fields
and could not. I exited only the browser portion, leaving the Mozilla mailer
function rolling along, reopened the browser and yepper, this time it let me
enter text. So, it's still sick. Ben
Well, this bug is alive and well with build number 2001100203 - gotta exit the
browser and then re-enter the browser to be able to enter information in the
"additional comments" field, and other fields. Into the trash can this one goes.

bbaetz this isn't a dup of 102176 .. reopening bug.

bclinger - none of us can seem to reproduce this problem. It does sound like a
Windows focus issue of some sort.

Cc'ing our focus/event gurus ... saari@netscape.com and joki@netscape.com. Chris
who is handling windows focus issues now?
Status: VERIFIED → UNCONFIRMED
Resolution: DUPLICATE → ---
An interesting feature of this bug is that it can be worked around by exiting
the browser window and opening it right back up. It does not require exiting the
browser completely - just the one the form is in. Another thing - click in the
form field to start typing and the cursor shows up there - like it is ready to
start work and when the typing starts, nothing happens. Close the window, open
another window and wow, it's like working. I am now test for this and the
bookmarks bugs whenever I download a new build.
Your description sounds a lot like the linux focus bug 84386.

Are you able to type in form text fields if you click in the URL bar, click in
another window (to completely take focus away from that browser window) and then
click back into a text widget in the browser window?
I just downloaded and installed build 2001100203. It opened as normal, with both
the mail and browser functions opening. From the mail window, click on the link
provided in an email and that action resulted in opening this window. I clicked
on the "additional comments" field and was able to enter data. I then opened up
a new window (it goes to my.yahoo.com) and came back to this window and
attempted to enter data in the "additional comments" field and was unable to do
so. I then repeated the steps, went to another window and came back to this one,
and was able to type, though my typing ended up in opening up a bookmark
creation screen, which I canceled out of. Upon canceling out of the bookmark
creation screen, I returned to this screen and attempted to enter data and was
unable to do so. I then exited the browser segment, reopened it, went ot the
mail function and clicked on this link again, and wow, it works fine now.

I mentioned the opening up of a bookmark creation screen - this happens on
occasion and like this bug, is one that is random.
Build number 2001100203 - the forms - still has a problem - cannot enter data
into the form. This time though, the first time the browser window was opened, I
could enter data into the "additional comments" field. The second time I tried,
I could not - I then opened up a new window and played a bit, went back to the
problem window and could not enter any data. I then exited the browser, leaving
the mail window open, then started the browser again, and gosh, it worked just
fine. Ben
Well, the "cannot fill in the form" bug also lives in this build, number
2001100303. I opened a couple of new windows, back and forth, and no luck.
Finally exited this window, the one I was trying to fill the form in with,
reopened it, and it worked fine. To get around the bug, the window needs to be
exited and then reopened.

*** This bug has been marked as a duplicate of 100130 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → DUPLICATE
Verified Dup
Status: RESOLVED → VERIFIED
Wow, this build, number 2001100493 - I can sucessfully fill in the blanks!
Thanks! Now, I bet you'll tell me this bug ain't gotten worked on at all
.................
Well guys, build number 2001100403 - still has the same dang problem. I tested
another "bug" and went to the screen to advise the results and I couldn't enter
the data in the "additional comments" field. So, the bottom line is, it ain't
fixed ...
Still a problem with build 2001100503
Still with build 2001100610
Still a problem with build number 2001100803
Still a problem with build 2001100903
Still a problem with build 2001101003.
I don't know if this is already reported; I have searched for it but couldn't 
find it.
In addition to this bug, I've encountered the following strange problem.
The problem described in this Bug are happening in build 20010131, but not all 
the time. It doesn't seem to be related with whether the browser has just 
started or not.
I have encountered the problem only on a form which is located in a frameset. I 
can't put the focus on a textfield with my mouse, or the keyboard. When I 
minimize the window, or go to another window, and go back again, and I repeat 
this for approx. two times, there is an actual focus on the first textfield.
But, when I want to place the focus anywhere else in the form (there are 10 
textfields in it), the browser won't let me. To go to the next formfield, only 
the tab-button has this effect. 
It is something that happens only with textfields. I can use the radiobuttons 
and selects on the form without any problem.

I hope this submit helps your work.

Regards,

dj_sane@hotmail.com
You need to log in before you can comment on or make changes to this bug.