Closed Bug 91222 Opened 23 years ago Closed 19 years ago

This form gets stuck on the next to last field

Categories

(Core :: DOM: Core & HTML, defect, P4)

x86
Windows 2000
defect

Tracking

()

RESOLVED INVALID
Future

People

(Reporter: dbradley, Unassigned)

References

()

Details

Don't know if this is just bad use of JS or a bug. But if I enter all the
information and then click back to one of the previous fields the cursor does
not remain. It gets pulled back to the message field.

Also under Linux I can move around as expected, but the character count never
gets updated.

I'm running a build that was pulled 7/17/01 at around 2pm.

Steps to reproduce:
1. Got to URL above
2. Type in a bogus phone number
3. Type in a from name
4. Type in a subject
5. Type in a message
6. Click back on phone number or some other field besides the message
7. Wait one second and watch the cursor move back to the message field.
Confirming on 2001071704 Win2k. They're constantly putting focus on that
textfield. Maybe Mozilla is the only browser that does this right? =.->

Over to DOM HTML.
Assignee: asa → jst
Component: Browser-General → DOM HTML
QA Contact: doronr → stummala
Behavior confirmed under linux too: the char count is never updated. Investigating.
Ok so the linux issue is pretty simple. They explicitely exclude all unix
platforms from running the counter by sniffing navigator.appVersion. However
Mozilla on linux runs that script just fine.
In that case I can reproduce the Win2k behavior on linux. Even worse, if I put
the caret in the bugzilla comments textfield, when the timer of the page fires,
the caret is sent back to the messages textfield, without any indication to the
user.
This is definitely a timer issue.
Should we file a new evangelism bug for the linux issue?
Future.
Target Milestone: --- → Future
isn't this form controls
Priority: -- → P4
Mass-reassigning bugs.
Assignee: jst → dom_bugs
URL unreachable, redirecting via script to:
http://lb1.netster.com/Index.asp?Site=YXR0d3Mtc2YuY29t

As there are no testcases, I´m resolving this bug as invalid.
Feel free to reopen, if testcase can be provided.

Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
Component: DOM: HTML → DOM: Core & HTML
QA Contact: stummala → general
You need to log in before you can comment on or make changes to this bug.