Closed
Bug 100130
Opened 23 years ago
Closed 23 years ago
Unable to enter/modify text in input fields
Categories
(Core :: DOM: Editor, defect)
Tracking
()
People
(Reporter: moz-bugzilla2, Assigned: saari)
References
()
Details
This is a bug that's hard to recreate but I have noticed it for a while with
Mozilla builds (it happened in today's Mozilla build) as well as Netscape 6.1.
I'm not sure when it began. What will happen is that I can not edit or enter
text in form fields on a page. I can't get it to let me insert new text or
modify text already there. One way I know to continue on is to press Ctrl-O and
then cancel that dialogue. The form fields in the page then become accessible.
Using other menu options might fix it, I need to test more. I think it mostly
happens when you first load the browser, but again it's hard to lock down
information on this problem. Have other people experienced this?
Reporter | ||
Updated•23 years ago
|
Summary: Unable to accept form text fields → Unable to enter/modify text in input fields
Comment 1•23 years ago
|
||
Reporter: Please see the bug reporting guidelines at
http://www.mozilla.org/quality/bug-writing-guidelines.html
It is very hard to diagnose problems without detailed information. Please post
BuildIDs and any URLs where this occurs with any kind of reprodcability.
Thanks
Reporter | ||
Comment 2•23 years ago
|
||
It happened twice for me today on 2001091703 on W2K. I've had it happen in
other builds. The URL it's happening for me is http://www.bantu.com/login.cfm
however I don't believe that page has anything to do it with. It's just that I
have that as my home page and thus it loads when I start Mozilla. I changed my
start page to Yahoo so will see if it happens with that some. I seem to notice
it when I load Mozilla thou it may have happened in other situations. You load
Mozilla and you can't add/modify/delete text in form input fields or in the URL
field.
Comment 3•23 years ago
|
||
WFM Win98SE 2001091703
Reporter | ||
Comment 4•23 years ago
|
||
Yes, unfortunately it works for me most of the time too, but it does happen a
few times a week for a while.
Reporter | ||
Comment 5•23 years ago
|
||
I put in a URL for a copy of the page which this happens on (the actual page is
on a private development server at my office). Unfortunately, it doesn't always
happen on it.
Comment 6•23 years ago
|
||
->editor
Assignee: asa → kin
Component: Browser-General → Editor: Core
QA Contact: doronr → sujay
Reporter | ||
Comment 7•23 years ago
|
||
Today this bug occurred again with different circumstances. I was running
today's build 2001092603 on W2K and I was on a google search page. I then went
to enter some text in the URL field. I entered www.bantu.office/l and then
clicked in the white space on the google page. I was then unable to enter teach
in either the google input field or the URL field. There is a problem with
this. Is there something I could do to give you more information on this? This
problem does not seem to be reliably reproducible, but it does occur.
*** Bug 102174 has been marked as a duplicate of this bug. ***
I haven't been able to reproduce this bug in form text widgets, but I'm hoping
it's related to bug 103197 which happens when bringing up new XUL dialogs/windows.
bclinger or steve, are you guys able to reproduce this problem without bringing
up a new browser window?
Assignee: kin → joki
Depends on: 103197
Comment 10•23 years ago
|
||
It normally occurs when the browser is first started and data attempted to be
entered in the first form field. It's happened in the "address line" a couple of
times. When you state "new window" does that mean a 2nd physical window or one
that is reached by clicking on a link and going to a different site? It's
happened both ways, though normally the first time the browser starts in the
first physical window, et cetera.
Comment 11•23 years ago
|
||
Still with build 2001100610
Comment 12•23 years ago
|
||
Still a problem with build number 2001100803
Comment 13•23 years ago
|
||
Still a problem with build 2001100903
Comment 14•23 years ago
|
||
Still a problem with build 2001101003.
Comment 15•23 years ago
|
||
bclinger: please stop posting daily status until we actually fix this bug...
thanks.
Comment 16•23 years ago
|
||
Fine. One too many pieces of email? Is there a place to watch the development?
or will a note be placed? or what?
Frankly, I had not idea that I was interfering with you doing your job and wish
to extend an apology.
Comment 17•23 years ago
|
||
you will receive notification via email for any activity on this bug...
thanks.
Comment 18•23 years ago
|
||
Don't waste your time nor mine.
Comment 19•23 years ago
|
||
bclinger, it looks like you are cc'd on all the pertinent bugs (bug 100130 and
in particular 103197), just watch your email for updates. Until then, we can
only assume that there has been no progress/movement on a solution for the bug
and that it is still present. Your efforts are appreciated, and I think an
occassional (not daily) status would be cool.
If this bug is preventing you from using Mozilla, we should probably raise the
severity and perhaps add keywords that can raise this bug to the top of the list
of priorities of whoever should be working on this.
The fact that you see this on a regular basis tells me that it is something that
needs to get fixed soon.
Saari can we get someone to look at this bug and 103197?
Reporter | ||
Comment 21•23 years ago
|
||
I'm still getting this with current builds. It seems like there has been no
activity on this in a month. Anything I can do to help the team get this fixed?
Comment 22•23 years ago
|
||
Looking at the initial report, it seems a dupe of bug 82534.
*** This bug has been marked as a duplicate of 82534 ***
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
•