Firefox 2 form issue

[JoeAtRevolutionUnltd]

When tabbing between fields on a contact form, you have to tab twice in order to move to the next field. I'm using jquery to validate the form. It works fine in ie7 and ff3. The page is

http://summit.jkdesign.com/contact-us

 

[vacunita]

I'm guessing tabbing twice is not what you want, but checking in Safari 3, Chrome, and IE8 all work as they are supposed to in addition to IE7 and FF3 that you already mentioned. So the question is:

What browser is it not working on?





----------------------------------
Ignorance is not necessarily Bliss, case in point:
Unknown has caused an Unknown Error on Unknown and must be shutdown to prevent damage to Unknown.

 

[vacunita]

Ahh never mind, I saw your post title.

FF2 is the one having problems.

Not sure why, it would be having trouble.

I'm guessing FF2 is running on a Windows Machine also?




----------------------------------
Ignorance is not necessarily Bliss, case in point:
Unknown has caused an Unknown Error on Unknown and must be shutdown to prevent damage to Unknown.

 

[spamjim]

If it is fine with FF3, then why worry about FF2?

FF is not installed by default on the two most popular operating systems. The user voluntarily installs it because they know better. If they know better, they would also keep their browser up-to-date.

A designer/developer should not stress over voluntary, obsolete software, especially if the issue is not a critical block to using your site.

 

[BillyRayPreachersSon]

If they know better, they would also keep their browser up-to-date.

I'm a web developer with over 10 years industry experience. I co-own a successful web development company with a very nice turnover. I have loads of posts under my belt here, and I'd say I know my onions.

Yet I use Fx 2 as my main browser, and have done for some time now.

I'll tell you why. Until very recently (I'd say January 2009), Fx 2 had more global users than Fx 3, so it made perfect sense to keep as my main browser the version of Fx that was more commonly in use.

Now that this has changed, I will look at moving Fx 2 into a VM, and upgrading to Fx 3 as my main browser... but probably not for another month or so.

To assume that people must somehow not know what they are doing if choosing to keep an 'older' browser is just not thinking. Would you still say I should know better?

Dan



Coedit Limited - Delivering standards compliant, accessible web solutions

Dan's Page [blue]@[/blue] Code Couch:

http://www.codecouch.com/dan/

Code Couch Tech Snippets & Info:

http://www.codecouch.com/

 

[BillyRayPreachersSon]

Oh - I forgot to mention, it works fine on my Fx 2 - only one tab keypress is needed to move from one field to the next.

However, the email validation script is clearly broken, as it is failing valid email addresses containing "+" signs. Perhaps reading thread216-1509660 could help with this?

Dan



Coedit Limited - Delivering standards compliant, accessible web solutions

Dan's Page [blue]@[/blue] Code Couch:

http://www.codecouch.com/dan/

Code Couch Tech Snippets & Info:

http://www.codecouch.com/

 

[BillyRayPreachersSon]

Odd - the validation seems to be working fine now - perhaps I just hadn't waited for all the script to load?



Coedit Limited - Delivering standards compliant, accessible web solutions

Dan's Page [blue]@[/blue] Code Couch:

http://www.codecouch.com/dan/

Code Couch Tech Snippets & Info:

http://www.codecouch.com/

 

[spamjim]

If you know better, then you wouldn't be upgrading to FF3, would you?

It seems a bit odd to be retaining FF2 in a VM if FF2 can run along FF3 at the same time on a single system.

The point of my post was to reflect necessity. There is no need to specifically design for an old browser if the functionality of the site is not jeopardized. The FF2 issue is nothing to worry about when we look at the greater picture.

If legacy browsers were an issue, we'd be discussing IE6 as well. This form does not allow any input under IE6. Try it.

 

[ca8msm]

The user voluntarily installs it because they know better. If they know better, they would also keep their browser up-to-date.

If that were true, then surely there would be no FF2 users now? I know from my website statistics that I still get a lot of hits from users on this browser, so why would it be different for anyone else? Even if you think they should have upgraded to FF3, I can say with some certainty that this isn't the case for a lot of users, so it's a perfectly valid argument for getting the user's site to work in this particular browser.

Mark,

[URL unfurl="true"]http://lessthandot.com[/url] - Experts, Information, Ideas & Knowledge
[URL unfurl="true"]http://mdssolutions.co.uk[/url] - Website Design
[URL unfurl="true"]http://aspnetlibrary.com[/url] - An online resource for professional ASP.NET developers

 

[spamjim]

Do not think I am insulting someone for a browser choice.

Not being able to tab is not a major block to using the web page in question. Web designers know better than to nitpick minor quirks if it does not affect the overall usability of a page. There is no way for us to be entirely backward compatible. FF2 users are not harmed by being unable to tab. If you want to be a power browser user that tabs through forms, you are most likely going to be a power user that keeps your browser up-to-date. Why is this topic so controversial? Check your site visitor statistics to see how many FF2 users tab rather than click in new form fields. This discussion over FF2 is a petty distraction.

Get your minds off of FF2 and look at IE6! That is where the real problem is.

As the problem involves jQuery, the javascript forum here at Tek-Tips may have more insight.
forum216

 

[spamjim]

I just tried this on a second system with IE6 and now it is working. Maybe the others that are hung up on assumed insults about users of FF2 can redirect their focus to confirming IE6 is okay.

 

[ca8msm]

I didn't take your comment to be insulting people for their browser choice; However, I couldn't understand why you thought it was acceptable to make it inaccessible for people to use their keyboard if they were using FF2 (which lots of people clearly are). I'd find that very annoying if I were using FF2 and the site wouldn't let me use my tab key.

Mark,

[URL unfurl="true"]http://lessthandot.com[/url] - Experts, Information, Ideas & Knowledge
[URL unfurl="true"]http://mdssolutions.co.uk[/url] - Website Design
[URL unfurl="true"]http://aspnetlibrary.com[/url] - An online resource for professional ASP.NET developers