Closed (fixed)
Project:
CAPTCHA
Version:
6.x-2.x-dev
Component:
User interface
Priority:
Minor
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
16 Mar 2007 at 23:42 UTC
Updated:
14 Nov 2010 at 22:37 UTC
When i feel out my user login form, first i type in my username and hit tab to go to password field and fill in password field.
When i hit tab again one should then be taken to the captcha input field to input an answer. However, the tab key takes you to the submit button instead.
Is there any way to fix this? It results in false submissions and really should be enabled..
NOTE: i'm using textimage as well
thanks
Comments
Comment #1
robloachIt would be good to get the tab indexes working. I know it's an issue with reCAPTCHA.
Comment #2
soxofaan commentedI looked through Drupal core and apparently only the user log in page form uses a tabindex (modules/user/user.module, line 889, function user_login()). So within Drupal core the issue only exists for the user log in page (?q=user).
Comment #3
newdru commentedSo i think what the both of you are saying is this:
1) Either captcha module needs to be modified to include a tabindex attribute on it's form widget input field so it gets inserted into the user form correctly and tabs work appropriately.
It sounds like if you enable tabindex that any field that doesn't use tabindex simply can not accept tab navigation - is that correct?
OR
2) Go into user module and delete the tab index attributes which removes that functionality from the user login form which allows tabs to work in their default nature for all fields?
Does this sound correct?
Comment #4
newdru commentedPossibly related question i posted here:
http://drupal.org/node/168471
that either of you two might be able to shed some light on. it's probably a js issue and is similar in that my arrow and enter keys don't work correctly on a given form field using autocomplete. I'd really love to solve this one. It's really annoying.
If noone has an outright answer, i'd at least love to be able to find a way to debug it using firebug or some other tool so i can figure out where it's going wrong!
thanks
Comment #5
soxofaan commentedThat are the possibilities indeed
option 2 seems bad style: poking in data from other modules when it's not really needed.
option 1: CAPTCHA should only add a tabindex to forms that have a tabindex on the submit button (e.g the user login page form), otherwise the taborder of forms without a tabindex on the submut button will break.
see http://www.w3.org/TR/html401/interact/forms.html#adef-tabindex for the specification of the tabindex behaviour
The problem is that CAPTCHA (in the general case) does not know the form element structure of a particular challenge in advance, and consequently has to guess to which element it has to add a tabindex to. The same applies to detecting the tabindex of the submit button. It's doable though.
In short: it can be solved, but there could be scenario's that it won't work (or it would be to involved/messy to make it work). We could at least support it for the user login page form.
Comment #6
soxofaan commentedat #4: that issue is not related, it's some Javascript issue, while tabindex is just a standard HTML thing.
Comment #7
newdru commentedI posted a reply to #4 in that thread if you can take a look.
Regarding this thread. The one thing that doesn't make sense according the html spec link is this. According to that document, even if a form element does NOT have tab index assigned to it, the tab keys should still eventually tab to it.
The behavior i was seeing isn't like that. You could keep tabbing until you looped the entire form over and over again and it just SKIPS the captch input field completely!
That document mentions that if a field is 'disabled' it will be skipped. But it doesn't say what constitutes a disabled field. What i'm seeing seems to be a captach field that behaves like it's "disabled" but still allows input?
Any clarifications?
thanks
Comment #8
newdru commentedI posted a reply to #4 in that thread if you can take a look.
Regarding this thread. The one thing that doesn't make sense according the html spec link is this. According to that document, even if a form element does NOT have tab index assigned to it, the tab keys should still eventually tab to it.
The behavior i was seeing isn't like that. You could keep tabbing until you looped the entire form over and over again and it just SKIPS the captcha input field entirely! In otherwords the tab key will never take the user to the captcha input field period!
That document mentions that if a field is 'disabled' it will be skipped. But that requires a specific 'disabled' attribute to be set on the element. And it doesn't appear to be the case because it still allows input?
Any clarifications?
thanks
Comment #9
agileware commented@newdru:
When I'm on the login screen I can tab to the captcha field. In the order it comes after the request new password tab. It's pretty much the last thing tabbed to on the screen.
Comment #10
soxofaan commentedI opened a issue against Drupal to remove the tabindex attributes:
#437930: remove tabindex attributes from user_login form
Comment #11
soxofaan commented#437930: remove tabindex attributes from user_login form was fixed for Drupal 7 and Drupal 6,
which solves the issue in this thread (at least for Drupal 6 and 7).
Comment #13
harish.rawat commentedHi all,
when i use this version iam not showing any captcha on user form.
how can i solve this? .
Comment #14
agileware commentedI would suggest searching for an issue that matches your problem and if you don't find one create a new one.
This issue is not the same as your problem so this is not the issue for you.
Also, support requests are not critical. - See http://drupal.org/node/156119