[solved] Register using Chrome 'emails do not match'
-
I get a very odd bug when trying to register a DevNet account using Google Chrome on Windows 7.
At this link: http://developer.qt.nokia.com/member/registerWhen I click submit with valid information, I receive: "The provided emails do not match".
However, there is only one email field. So, do not match with what?It works fine on Opera.
I hope this is the right place to mention this.
-
can you also mention which version of chrome you are using
-
chrome 9.0.587 might not be supported ... its the latest I guess ?
I'm on 7.0.517.44 and captcha works there ...
or switch to FF :) -
reCaptcha: Kaheld Gui. ; Table Hoposes ; Apsche money
I entered "test" instead. I even tried leaving it blank -- this also works.Result:
Thank You!Your registration has been successfully completed.
You have just been sent an email containing membership activation instructions.
OS: Windows 7; Browser: Google Chrome 7.0.517.44, 8.0.522.210, Opera 10.63
-
Just a mention that as of today Google Chrome 8.0.552.215 is considered the 'Stable' version and Google Chrome 9 is now the 'Beta' version.
I think 9 has some issues due to its 'sandbox'.Anyway, Captcha is definitely not working. Surprised it isn't reproducible.
-
I don't know if it is assumed as solved, but i just tried to make an account and this problem happened to me.
The problem happens because the form input for the confirmation email is "hidden".
I had to use the element inspector, change its properties to text. With this i could inform my email, register and notify this bug!I was using Chromium 8.0.552.237
Posting using Firefox because the "Post Reply" wasn't working on the Chromium (another bug). -
[quote author="leokolln" date="1295737009"]The problem happens because the form input for the confirmation email is "hidden".
I had to use the element inspector, change its properties to text. With this i could inform my email, register and notify this bug![/quote]We have changed the way that part of the registration form works now. The error you had was because the JavaScript that fills in the confirmation field didn't execute for some reason. The new form handles this on the server side.