I really like the option to check the username via AJAX (Module Configuration-->Validation Configuration) BUT I do not like how it corrupts the focus afterwards.

Normally while registering you can enter text and press TAB to move to the next textbox.  But, when AJAX username checking is turned on, after you enter the username and press TAB the usual validation text is displayed next to the username textbox and the focus is put on the DNN copyright message at the bottom of the page.  Of course, the focus should be placed on the next textbox (password in my instance).

It's probably just a quirk with my installation since I can't imagine this issue getting past the module testers.

In any case, I assume the only way to fix the bug is to buy the source code and modify it directly.

Hi,

Yes well the AJAX username check is a very new feature that was just added to the 3.2 release. Although the development matches with the initial design of the enhancement, we hope to improve it in future releases. First, although normally the focus should always be on the next field it does lose focus after the function call is running. We are still researching to find out the best way to fix this, we could easily add code to set the focus for another field but I am not sure if this field needs to be defined in the module configuration area or if its better to find out which field represents the next field after username to set focus there.

As far as speed... The faster the server and hosting account you are on, the faster the AJAX check should last. Keep in mind though that it does have to do a database call via AJAX and check to see if the username is available. The more users you have in the database, the longer this process will take. This was very quick during testing with 50 users on the system, but if you have a few thousand this is going to take longer.

Finally... Another enhancement for this might be to combine the focus with another message that is also displaying when the AJAX function is performing. Something like 'Checking username....'


We plan to add similar features with password validation, similar to implementations where you see 'Very Secure' or 'Weak' etc... So we will probably want to iron out the username check feature first before we add this one, however this feature isn't doing any database calls so it should be much faster.


-Chad

I am experiencing this problem too, but I believe the problem is that it isn't actually doing an AJAX callback and is doing a full page reload instead.  I've checked what is happening in the browser using the ieHttpHeaders add-in to monitor the requests that are being made and it certainly looks like a full page reload is being done.

Jason