What has happened to Firefox?

We have a form that has been functioning without issue since 2008. All of a sudden in Firefox (and Chrome) it decides on its own where the cursor should be. If the user tries to click into a different field, the cursor jumps back to the first field. We've tried adding "onblur - set focus", but if the entries are made out of order, the form ignores where the user wants to go and decides where it thinks it should go. This is not a problem in IE.
slegyAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Dave BaldwinFixer of ProblemsCommented:
I am not seeing any odd behavior in any browser.  And without a link to your form page, we can't investigate it and suggest any solutions.  Have you checked it with the W3C Validator to make sure your code is correct?
0
slegyAuthor Commented:
Here is the link to the page: http://www.lightningclass.org/membership/joinRenew/membershipFleet.asp

The page has been running in pretty much the same form since 2008, and only recently have problems been reported. Before doing anything, you can put your cursor in any field, and it immediately focuses back to the Fleet Dues. You can select a fleet number and then move the cursor the Fleet Captain box, but the cursor jumps to the Fleet Dues field - and it won't go any place else. There is no code setting the focus to that field. In checking the code. it only reported "expanding box problem."
0
Dave BaldwinFixer of ProblemsCommented:
I think the problem is related to 'tabindex' and the fact that 'Fleet Dues' does not have one.  From https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/tabindex

An element with a 0 value, an invalid value, or no tabindex value should be placed after elements with a positive tabindex in the sequential keyboard navigation order.

I think you should either remove all 'tabindex' attributes or add one to 'Fleet Dues' to put it in the correct order.  I never use 'tabindex' in my forms.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
slegyAuthor Commented:
Thank you. I didn't put tab indexes on fields that are display only. Had no idea that would be a problem. Thank you for the help.
0
Dave BaldwinFixer of ProblemsCommented:
You're welcome, glad to help.  I didn't know it would that way until I looked at your page.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Web Browsers

From novice to tech pro — start learning today.