Quote:
Originally Posted by Coders Shack
not sure what your talking about
|
It doesn't happen at home using FF but at work using ie6.
Seems to me that the new form breaks on certain browsers which is a bit of a problem as far as I'm concerned

.
The new functionality of having a timeout on the input fields really doesn't work out too well from my point of view. I do like what you're trying to do, but how about it being on a lower timeout but not switching fields and making the "completed" field "done" ?
This way you could type in:
usern -> wait a bit and consider while getting the message that it's free -> complete it to username and get a new update (could possibly store 'usern' as a var and compare it to 'username' and if they're different do a new check and output new result to user).
Basically it needs to update the status either with a button or close to realtime, this artificial delay just feels really weird.