Closed
Bug 209060
Opened 22 years ago
Closed 20 years ago
onChange tab control doesn't work as expected.
Categories
(Toolkit :: Form Manager, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: prodgers, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3.1) Gecko/20030425
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3.1) Gecko/20030425
I needed to cause a tab or enter depression to hop to a specific box. This
workaround solved the problem of the form being submitted on enter as well. I
used the following code:
onChange="document.reservationForm.studentnumber.focus()"
This does appear to hop to the appropriate text box, but when you begin to enter
data you find it is, in fact, on the next active link rather than the
appropriate textbox or textarea.
This event handler works in IE 5.5 as well as Netscape 4.7.
Reproducible: Always
Steps to Reproduce:
1. Enter data in any textbox/textarea (not checkboxes)
2. Hit the Tab or Enter key
3.
Actual Results:
It appeared to hop to the textbox/textarea specified in the code. However, when
I began entering data, the cursor was actually located on the active link just
before the textbox/textarea - what would be the default location if you had no
coding and used the tab to move around the form.
Expected Results:
Both IE and Netscape 4.7 moved the cursor to the textbox/textarea specified in
the coding.
Updated•20 years ago
|
Assignee: dveditz → nobody
Comment 1•20 years ago
|
||
This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 2•20 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•